Check DNS, Urls + Redirects, Certificates and Content of your Website

0 in Queue, 2 of max. 8 Checks (14:32:22)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

A

 

Top config

 

Checked:
28.08.2021 21:40:28

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
git.yadle.com
A
104.155.133.20
Council Bluffs/Iowa/United States (US) - Google LLC
Hostname: 20.133.155.104.bc.googleusercontent.com
yes
1
0

AAAA

yes


www.git.yadle.com

Name Error
yes
1
0
*.yadle.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.git.yadle.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=






• Status: Valid because published






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 26838, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 10.09.2021, 00:00:00 +, Signature-Inception: 20.08.2021, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: com

com
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.09.2021, 17:00:00 +, Signature-Inception: 28.08.2021, 16:00:00 +, KeyTag 26838, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26838 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 39343, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.09.2021, 18:24:21 +, Signature-Inception: 28.08.2021, 18:19:21 +, KeyTag 30909, Signer-Name: com






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: yadle.com

yadle.com
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "in2k606ovp7g6tug8ldc26aa5tfaf910" between the hashed NSEC3-owner "in2juhtd5803c0msrrmvqv4ui34slpqh" and the hashed NextOwner "in2l55vq6lf62ufd5ck62teerdec69mb". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner in2juhtd5803c0msrrmvqv4ui34slpqh.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 04.09.2021, 04:45:50 +, Signature-Inception: 28.08.2021, 03:35:50 +, KeyTag 39343, Signer-Name: com






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "yadle.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.09.2021, 04:25:04 +, Signature-Inception: 25.08.2021, 03:15:04 +, KeyTag 39343, Signer-Name: com






0 DNSKEY RR found









Zone: git.yadle.com

git.yadle.com
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.git.yadle.com

www.git.yadle.com
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.git.yadle.com
•  ns49.domaincontrol.com

git.yadle.com
•  ns49.domaincontrol.com / p15
97.74.104.25
Scottsdale/Arizona/United States (US) - Host Europe GmbH		•

• 
2603:5:2182::19
New York/United States (US) - Host Europe GmbH		•
yadle.com
•  ns49.domaincontrol.com / s01
97.74.104.25
Scottsdale/Arizona/United States (US) - Host Europe GmbH		•

• 
2603:5:2182::19
New York/United States (US) - Host Europe GmbH		•

•  ns50.domaincontrol.com / p10
173.201.72.25
Scottsdale/Arizona/United States (US) - Host Europe GmbH		•

• 
2603:5:2282::19
New York/United States (US) - Host Europe GmbH		•
com
•  a.gtld-servers.net / nnn1-fra6
•

•  b.gtld-servers.net / nnn1-eltxl2
•

•  c.gtld-servers.net / nnn1-fra6
•

•  d.gtld-servers.net / nnn1-fra6
•

•  e.gtld-servers.net / nnn1-fra6
•

•  f.gtld-servers.net / nnn1-fra5
•

•  g.gtld-servers.net / nnn1-fra5
•

•  h.gtld-servers.net / nnn1-fra5
•

•  i.gtld-servers.net / nnn1-fra5
•

•  j.gtld-servers.net / nnn1-ein5
•

•  k.gtld-servers.net / nnn1-ein4
•

•  l.gtld-servers.net / nnn1-ein5
•

•  m.gtld-servers.net / nnn1-ein1
•

 

4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1630179608
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:12


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1630179623
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:1


Domain:yadle.com
Zone-Name:yadle.com
Primary:ns49.domaincontrol.com
Mail:dns.jomax.net
Serial:2021072307
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


Domain:git.yadle.com
Zone-Name:yadle.com
Primary:ns49.domaincontrol.com
Mail:dns.jomax.net
Serial:2021072307
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:2


Domain:www.git.yadle.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://git.yadle.com/users/sign_in, address used: https://git.yadle.com/users/sign_in, Screenshot created 2021-08-28 21:42:00 +00:0

 

Mobil (412px x 732px)

 

492 milliseconds

 

Screenshot mobile - https://git.yadle.com/users/sign_in
Mobil + Landscape (732px x 412px)

 

542 milliseconds

 

Screenshot mobile landscape - https://git.yadle.com/users/sign_in
Screen (1280px x 1680px)

 

1419 milliseconds

 

Screenshot Desktop - https://git.yadle.com/users/sign_in

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport396732
content Size396761

 

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

 

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_256_GCM.

 

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://git.yadle.com/
104.155.133.20
301
https://git.yadle.com:443/
Html is minified: 109.46 %
0.240
A
Server: nginx
Date: Sat, 28 Aug 2021 19:41:11 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://git.yadle.com:443/

• https://git.yadle.com/
104.155.133.20
302
https://git.yadle.com/users/sign_in
Html is minified: 100.00 %
3.790
A
Server: nginx
Date: Sat, 28 Aug 2021 19:41:12 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 101
Connection: close
Cache-Control: no-cache
Location: https://git.yadle.com/users/sign_in
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: DENY
X-Gitlab-Feature-Category: projects
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 01FE74FG32C5M0YMTXJ6M307EZ
X-Runtime: 0.023708
X-Ua-Compatible: IE=edge
X-Xss-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000
Referrer-Policy: strict-origin-when-cross-origin

• https://git.yadle.com:443/

302
https://git.yadle.com/users/sign_in
Html is minified: 100.00 %
3.333
A
Server: nginx
Date: Sat, 28 Aug 2021 19:41:21 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 101
Connection: close
Cache-Control: no-cache
Location: https://git.yadle.com/users/sign_in
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: DENY
X-Gitlab-Feature-Category: projects
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 01FE74FRXG28AGMXC0Z1ZK6NH4
X-Runtime: 0.011426
X-Ua-Compatible: IE=edge
X-Xss-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000
Referrer-Policy: strict-origin-when-cross-origin

• https://git.yadle.com/users/sign_in

Inline-JavaScript (∑/total): 3/544 Inline-CSS (∑/total): 1/43751		200

Html is minified: 660.83 %
Other inline scripts (∑/total): 3/544		3.380
A
small visible content (num chars: 326)
GitLab A complete DevOps platform GitLab is a single application for the entire software development lifecycle. From project planning and source code management to CI/CD, monitoring, and security. This is a self-managed instance of GitLab. Username or email Password Remember me Forgot your password? Explore Help About GitLab
Server: nginx
Date: Sat, 28 Aug 2021 19:41:25 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: max-age=0, private, must-revalidate
Etag: W/"cebc8cc092a8c975cfc6c480f83dc938"
Permissions-Policy: interest-cohort=()
Set-Cookie: _gitlab_session=766f31cebdaf05b518809d52f65887ba; path=/; expires=Sat, 28 Aug 2021 21:41:25 GMT; secure; HttpOnly; SameSite=None
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: DENY
X-Gitlab-Feature-Category: authentication_and_authorization
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 01FE74FWZ5AQ1AKAQSV2BJXYVM
X-Runtime: 0.045580
X-Ua-Compatible: IE=edge
X-Xss-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000
Referrer-Policy: strict-origin-when-cross-origin
Content-Encoding: gzip

• http://git.yadle.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
104.155.133.20
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 110.61 %
Other inline scripts (∑/total): 0/0		0.237
A
Not Found
Visible Content: 404 Not Found nginx
Server: nginx
Date: Sat, 28 Aug 2021 19:41:16 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://104.155.133.20/
104.155.133.20
302
https://104.155.133.20/users/sign_in
Html is minified: 100.00 %
3.540
N
Certificate error: RemoteCertificateNameMismatch
Server: nginx
Date: Sat, 28 Aug 2021 19:41:16 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 102
Connection: close
Cache-Control: no-cache
Location: https://104.155.133.20/users/sign_in
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: DENY
X-Gitlab-Feature-Category: projects
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 01FE74FMS3JMP9FXV81Z6BW0FM
X-Runtime: 0.011515
X-Ua-Compatible: IE=edge
X-Xss-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000
Referrer-Policy: strict-origin-when-cross-origin

• https://104.155.133.20/users/sign_in

Inline-JavaScript (∑/total): 3/544 Inline-CSS (∑/total): 1/43751		200

Html is minified: 660.47 %
Other inline scripts (∑/total): 3/544		3.340
N
Certificate error: RemoteCertificateNameMismatch
small visible content (num chars: 326)
GitLab A complete DevOps platform GitLab is a single application for the entire software development lifecycle. From project planning and source code management to CI/CD, monitoring, and security. This is a self-managed instance of GitLab. Username or email Password Remember me Forgot your password? Explore Help About GitLab
Server: nginx
Date: Sat, 28 Aug 2021 19:41:29 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Cache-Control: max-age=0, private, must-revalidate
Etag: W/"750920e7e62605ebd594232d544557f5"
Permissions-Policy: interest-cohort=()
Set-Cookie: _gitlab_session=8d3d12c4e40c8476504e9cc6e95a0d1f; path=/; expires=Sat, 28 Aug 2021 21:41:29 GMT; secure; HttpOnly; SameSite=None
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: DENY
X-Gitlab-Feature-Category: authentication_and_authorization
X-Permitted-Cross-Domain-Policies: none
X-Request-Id: 01FE74G125ZWTQK5SQ4FBAKMY7
X-Runtime: 0.035485
X-Ua-Compatible: IE=edge
X-Xss-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000
Referrer-Policy: strict-origin-when-cross-origin
Content-Encoding: gzip

 

7. Comments


1. General Results, most used to calculate the result

Aname "git.yadle.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 61113 (complete: 168171)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: git.yadle.com has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: git.yadle.com has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
Ahttps://git.yadle.com:443/
302
https://git.yadle.com/users/sign_in
Correct redirect https to https
Ahttps://git.yadle.com/ 104.155.133.20
302
https://git.yadle.com/users/sign_in
Correct redirect https to https
Ahttps://104.155.133.20/ 104.155.133.20
302
https://104.155.133.20/users/sign_in
Correct redirect https to https
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
AGood: every cookie sent via https is marked as secure
AGood: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None
AGood: every https has a Strict Transport Security Header
AGood: HSTS max-age is long enough, 31536000 seconds = 365 days
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (3 urls)
http://git.yadle.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.155.133.20


Url with incomplete Content-Type - header - missing charset
Nhttps://104.155.133.20/ 104.155.133.20
302
https://104.155.133.20/users/sign_in
Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://104.155.133.20/users/sign_in
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain git.yadle.com, 1 ip addresses, 1 different http results.

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 27 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 27 Queries complete, 27 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 13.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns49.domaincontrol.com, ns50.domaincontrol.com, 2 Name Servers included in Delegation: ns49.domaincontrol.com, ns50.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns49.domaincontrol.com, ns50.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns49.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns49.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns49.domaincontrol.com.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns49.domaincontrol.com, ns50.domaincontrol.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: domaincontrol.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.72., 97.74.104.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:2182:, 2603:0005:2282:, 2 different subnets (first four blocks): 2603:0005:2182:0000:, 2603:0005:2282:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns49.domaincontrol.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://git.yadle.com/users/sign_in
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://104.155.133.20/users/sign_in
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://git.yadle.com/users/sign_in
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://104.155.133.20/users/sign_in
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
AGood: All script Elements (type text/javascript) and src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
AGood: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 8 external CSS / JavaScript files found
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 8 external CSS / JavaScript files without Cache-Control-Header, 8 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 16 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 99647 milliseconds, 99.647 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
git.yadle.com
git.yadle.com
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
git.yadle.com
git.yadle.com
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=git.yadle.com


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


git.yadle.com
104.155.133.20
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

git.yadle.com
104.155.133.20
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=git.yadle.com


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


104.155.133.20
104.155.133.20
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

104.155.133.20
104.155.133.20
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=git.yadle.com


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


104.155.133.20
104.155.133.20
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

104.155.133.20
104.155.133.20
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=git.yadle.com


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US

 

9. Certificates

1.
1.
CN=git.yadle.com
21.08.2021
19.11.2021
1213 days expired		git.yadle.com - 1 entry
1.
1.
CN=git.yadle.com
21.08.2021

19.11.2021
1213 days expired


git.yadle.com - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:04FD6D6095B02B34429BFA8CCBE24F640957
Thumbprint:C9D95C0CEF807281F508100BECEF41E90FF5CD40
SHA256 / Certificate:75mo3TckkREOBA8QyPBHqJBUgZn86Y7opDgEzg+raIo=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):1ca682f5ab7292e0b0062c5e290d3a182986087c0fc06fbdc85c24f65c3e612a
SHA256 hex / Subject Public Key Information (SPKI):1ca682f5ab7292e0b0062c5e290d3a182986087c0fc06fbdc85c24f65c3e612a (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://r3.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 183 days

2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020

15.09.2025
expires in 183 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3732 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3732 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Small Code Update - wait one minute

 

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Small Code Update - wait one minute

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns49.domaincontrol.com, ns50.domaincontrol.com

 

QNr.DomainTypeNS used
1
com
NS
l.root-servers.net (2001:500:9f::42)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns49.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35
3
ns50.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35
4
net
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
5
a1-245.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a9-67.akam.net
184.85.248.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a11-67.akam.net
84.53.139.67

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43
6
a11-64.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a12-67.akam.net
184.26.160.67

Answer: a11-67.akam.net
84.53.139.67

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
7
a20-65.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
8
a6-66.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
9
a8-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67
10
a4-67.akam.net: 72.246.46.67
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
11
a6-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a4-67.akam.net
72.246.46.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
12
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
13
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
14
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
15
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
16
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
17
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
18
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
19
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
20
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
21
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
22
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
23
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
24
ns49.domaincontrol.com: 97.74.104.25
A
a1-245.akam.net (2600:1401:2::f5)
25
ns49.domaincontrol.com: 2603:5:2182::19
AAAA
a1-245.akam.net (2600:1401:2::f5)
26
ns50.domaincontrol.com: 173.201.72.25
A
a1-245.akam.net (2600:1401:2::f5)
27
ns50.domaincontrol.com: 2603:5:2282::19
AAAA
a1-245.akam.net (2600:1401:2::f5)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
git.yadle.com
0

no CAA entry found
1
0
yadle.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
yadle.com
google-site-verification=Vbn5dYyV8Y9d29aQUTx3kAXg5PyAWfWCrt9SBUAMP-o
ok
1
0
yadle.com
postman-domain-verification=9952faa3a5e3215ae129c43571cb4527e0613625f60b1ccd8b922552191edb8e368dc6e944a89766dbfa1c8114554f743818ade91fb24463bac6d9e91d475ca6
ok
1
0
git.yadle.com

ok
1
0
_acme-challenge.git.yadle.com

Name Error - The domain name does not exist
1
0
_acme-challenge.git.yadle.com.yadle.com

Name Error - The domain name does not exist
1
0
_acme-challenge.git.yadle.com.git.yadle.com

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
git.yadle.com
104.155.133.20
21
FTP



git.yadle.com
104.155.133.20
21
FTP



git.yadle.com
104.155.133.20
22
SSH



git.yadle.com
104.155.133.20
22
SSH



git.yadle.com
104.155.133.20
25
SMTP



git.yadle.com
104.155.133.20
25
SMTP



git.yadle.com
104.155.133.20
53
DNS



git.yadle.com
104.155.133.20
53
DNS



git.yadle.com
104.155.133.20
110
POP3



git.yadle.com
104.155.133.20
110
POP3



git.yadle.com
104.155.133.20
143
IMAP



git.yadle.com
104.155.133.20
143
IMAP



git.yadle.com
104.155.133.20
465
SMTP (encrypted)



git.yadle.com
104.155.133.20
465
SMTP (encrypted)



git.yadle.com
104.155.133.20
587
SMTP (encrypted, submission)



git.yadle.com
104.155.133.20
587
SMTP (encrypted, submission)



git.yadle.com
104.155.133.20
993
IMAP (encrypted)



git.yadle.com
104.155.133.20
993
IMAP (encrypted)



git.yadle.com
104.155.133.20
995
POP3 (encrypted)



git.yadle.com
104.155.133.20
995
POP3 (encrypted)



git.yadle.com
104.155.133.20
1433
MS SQL



git.yadle.com
104.155.133.20
1433
MS SQL



git.yadle.com
104.155.133.20
2082
cPanel (http)



git.yadle.com
104.155.133.20
2082
cPanel (http)



git.yadle.com
104.155.133.20
2083
cPanel (https)



git.yadle.com
104.155.133.20
2083
cPanel (https)



git.yadle.com
104.155.133.20
2086
WHM (http)



git.yadle.com
104.155.133.20
2086
WHM (http)



git.yadle.com
104.155.133.20
2087
WHM (https)



git.yadle.com
104.155.133.20
2087
WHM (https)



git.yadle.com
104.155.133.20
2089
cPanel Licensing



git.yadle.com
104.155.133.20
2089
cPanel Licensing



git.yadle.com
104.155.133.20
2095
cPanel Webmail (http)



git.yadle.com
104.155.133.20
2095
cPanel Webmail (http)



git.yadle.com
104.155.133.20
2096
cPanel Webmail (https)



git.yadle.com
104.155.133.20
2096
cPanel Webmail (https)



git.yadle.com
104.155.133.20
2222
DirectAdmin (http)



git.yadle.com
104.155.133.20
2222
DirectAdmin (http)



git.yadle.com
104.155.133.20
2222
DirectAdmin (https)



git.yadle.com
104.155.133.20
2222
DirectAdmin (https)



git.yadle.com
104.155.133.20
3306
mySql



git.yadle.com
104.155.133.20
3306
mySql



git.yadle.com
104.155.133.20
5224
Plesk Licensing



git.yadle.com
104.155.133.20
5224
Plesk Licensing



git.yadle.com
104.155.133.20
5432
PostgreSQL



git.yadle.com
104.155.133.20
5432
PostgreSQL



git.yadle.com
104.155.133.20
8080
Ookla Speedtest (http)



git.yadle.com
104.155.133.20
8080
Ookla Speedtest (http)



git.yadle.com
104.155.133.20
8080
Ookla Speedtest (https)



git.yadle.com
104.155.133.20
8080
Ookla Speedtest (https)



git.yadle.com
104.155.133.20
8083
VestaCP http



git.yadle.com
104.155.133.20
8083
VestaCP http



git.yadle.com
104.155.133.20
8083
VestaCP https



git.yadle.com
104.155.133.20
8083
VestaCP https



git.yadle.com
104.155.133.20
8443
Plesk Administration (https)



git.yadle.com
104.155.133.20
8443
Plesk Administration (https)



git.yadle.com
104.155.133.20
8447
Plesk Installer + Updates



git.yadle.com
104.155.133.20
8447
Plesk Installer + Updates



git.yadle.com
104.155.133.20
8880
Plesk Administration (http)



git.yadle.com
104.155.133.20
8880
Plesk Administration (http)



git.yadle.com
104.155.133.20
10000
Webmin (http)



git.yadle.com
104.155.133.20
10000
Webmin (http)



git.yadle.com
104.155.133.20
10000
Webmin (https)



git.yadle.com
104.155.133.20
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=37523d4a-57f6-4bfa-82c0-a8aa8a7f675c

 

Last Result: https://check-your-website.server-daten.de/?q=git.yadle.com - 2021-08-28 21:40:28

 

Do you like this page? Support this tool, add a link on your page:

 

<a href="https://check-your-website.server-daten.de/?q=git.yadle.com" target="_blank">Check this Site: git.yadle.com</a>

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=git.yadle.com

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions