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


 

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cn2.8989898.xyz
A
93.179.118.246
Los Angeles/California/United States (US) - IT7 Networks Inc
Hostname: 93.179.118.246.16clouds.com
yes
1
0

AAAA

yes


www.cn2.8989898.xyz

Name Error
yes
1
0
*.8989898.xyz
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.cn2.8989898.xyz
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 9799, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 13.03.2022, 00:00:00 +, Signature-Inception: 20.02.2022, 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: xyz

xyz
2 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 3599, DigestType 1 and Digest P6OyZPRdtfOL7erxqIt2qjGMLH8=






DS with Algorithm 8, KeyTag 3599, DigestType 2 and Digest uXM4abyEyGu1nRArpdprJ7IIhVIzKjnc1UvE6NZrBJk=






1 RRSIG RR to validate DS RR found






RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.03.2022, 05:00:00 +, Signature-Inception: 23.02.2022, 04:00:00 +, KeyTag 9799, Signer-Name: (root)






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






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 12489, Flags 256






Public Key with Algorithm 8, KeyTag 43218, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 24.03.2022, 13:19:36 +, Signature-Inception: 22.02.2022, 12:44:49 +, KeyTag 3599, Signer-Name: xyz






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






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






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



Zone: 8989898.xyz

8989898.xyz
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 12062, DigestType 1 and Digest kOwodVYWvbXXn+OB0xuwkatsG5w=






1 RRSIG RR to validate DS RR found






RRSIG-Owner 8989898.xyz., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 25.03.2022, 01:35:34 +, Signature-Inception: 22.02.2022, 12:44:49 +, KeyTag 12489, Signer-Name: xyz






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 12062, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 13, KeyTag 36645, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner 8989898.xyz., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 03.03.2022, 00:00:00 +, Signature-Inception: 10.02.2022, 00:00:00 +, KeyTag 12062, Signer-Name: 8989898.xyz






Status: Good - Algorithmus 13 and DNSKEY with KeyTag 12062 used to validate the DNSKEY RRSet






Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 12062, DigestType 1 and Digest "kOwodVYWvbXXn+OB0xuwkatsG5w=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: cn2.8989898.xyz

cn2.8989898.xyz
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "cn2.8989898.xyz" and the NextOwner "cn2v.8989898.xyz". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC, CAA






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 93.179.118.246
Validated: RRSIG-Owner cn2.8989898.xyz., Algorithm: 13, 3 Labels, original TTL: 1799 sec, Signature-expiration: 03.03.2022, 00:00:00 +, Signature-Inception: 10.02.2022, 00:00:00 +, KeyTag 36645, Signer-Name: 8989898.xyz






RRSIG Type 257 validates the CAA - Result: 5|issueletsencrypt.org
Validated: RRSIG-Owner cn2.8989898.xyz., Algorithm: 13, 3 Labels, original TTL: 1799 sec, Signature-expiration: 03.03.2022, 00:00:00 +, Signature-Inception: 10.02.2022, 00:00:00 +, KeyTag 36645, Signer-Name: 8989898.xyz






CNAME-Query sends a valid NSEC RR as result with the query name "cn2.8989898.xyz" equal the NSEC-owner "cn2.8989898.xyz" and the NextOwner "cn2v.8989898.xyz". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC, CAA Validated: RRSIG-Owner cn2.8989898.xyz., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 03.03.2022, 00:00:00 +, Signature-Inception: 10.02.2022, 00:00:00 +, KeyTag 36645, Signer-Name: 8989898.xyz






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC RR as result with the query name "cn2.8989898.xyz" equal the NSEC-owner "cn2.8989898.xyz" and the NextOwner "cn2v.8989898.xyz". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC, CAA Validated: RRSIG-Owner cn2.8989898.xyz., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 03.03.2022, 00:00:00 +, Signature-Inception: 10.02.2022, 00:00:00 +, KeyTag 36645, Signer-Name: 8989898.xyz






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC RR as result with the query name "cn2.8989898.xyz" equal the NSEC-owner "cn2.8989898.xyz" and the NextOwner "cn2v.8989898.xyz". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC, CAA Validated: RRSIG-Owner cn2.8989898.xyz., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 03.03.2022, 00:00:00 +, Signature-Inception: 10.02.2022, 00:00:00 +, KeyTag 36645, Signer-Name: 8989898.xyz






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.cn2.8989898.xyz) sends a valid NSEC RR as result with the owner name cn2.8989898.xyz. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "cn2.8989898.xyz" and the NextOwner "cn2v.8989898.xyz". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.cn2.8989898.xyz) sends a valid NSEC RR as result with the query name "_443._tcp.cn2.8989898.xyz" between the NSEC-owner "cn2.8989898.xyz" and the NextOwner "cn2v.8989898.xyz". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.cn2.8989898.xyz) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.cn2.8989898.xyz" between the NSEC-owner "cn2.8989898.xyz" and the NextOwner "cn2v.8989898.xyz". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: A, RRSIG, NSEC, CAA Validated: RRSIG-Owner cn2.8989898.xyz., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 03.03.2022, 00:00:00 +, Signature-Inception: 10.02.2022, 00:00:00 +, KeyTag 36645, Signer-Name: 8989898.xyz






Status: Good. NXDomain-Proof required and found.



Zone: www.cn2.8989898.xyz

www.cn2.8989898.xyz
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "cn2.8989898.xyz" and the NextOwner "cn2v.8989898.xyz". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC, CAA

 

3. Name Servers

DomainNameserverNS-IP
www.cn2.8989898.xyz
  dns1.registrar-servers.com

cn2.8989898.xyz
  dns1.registrar-servers.com / Flash_Auth_Host2.Amsterdam_Node1
2610:a1:1024::200
San Jose/California/United States (US) - NeuStar, Inc.

8989898.xyz
  dns1.registrar-servers.com / Flash_Auth_Host1.Amsterdam_Node1
2610:a1:1024::200
San Jose/California/United States (US) - NeuStar, Inc.


  dns2.registrar-servers.com / Flash_Auth_Host1.Frankfurt_Node1
2610:a1:1025::200
Fort Lauderdale/Florida/United States (US) - NeuStar, Inc.

xyz
  generationxyz.nic.xyz / CKQV-6AF162-DWW7G4


  ns0.centralnic.net


  x.nic.xyz / CEQY-QU41GH-6UZLZF


  y.nic.xyz / TAGD-KTE43F-5A9QX6


  z.nic.xyz / SFQY-BG7AF9-XTW0MS

 

4. SOA-Entries


Domain:xyz
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:xyz
Zone-Name:xyz
Primary:ns0.centralnic.net
Mail:hostmaster.centralnic.net
Serial:3000660166
Refresh:900
Retry:1800
Expire:6048000
TTL:3600
num Entries:4


Domain:8989898.xyz
Zone-Name:8989898.xyz
Primary:dns1.registrar-servers.com
Mail:hostmaster.registrar-servers.com
Serial:1645531297
Refresh:43200
Retry:3600
Expire:604800
TTL:3601
num Entries:2


Domain:cn2.8989898.xyz
Zone-Name:8989898.xyz
Primary:dns1.registrar-servers.com
Mail:hostmaster.registrar-servers.com
Serial:1645531297
Refresh:43200
Retry:3600
Expire:604800
TTL:3601
num Entries:1


Domain:www.cn2.8989898.xyz
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://cn2.8989898.xyz, address used: https://cn2.8989898.xyz/, Screenshot created 2022-02-23 15:44:27 +00:0

 

Mobil (412px x 732px)

 

121 milliseconds

 

Screenshot mobile - https://cn2.8989898.xyz/
Mobil + Landscape (732px x 412px)

 

124 milliseconds

 

Screenshot mobile landscape - https://cn2.8989898.xyz/
Screen (1280px x 1680px)

 

228 milliseconds

 

Screenshot Desktop - https://cn2.8989898.xyz/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

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_128_GCM.

 

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

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://cn2.8989898.xyz/
93.179.118.246
301
https://cn2.8989898.xyz/
Html is minified: 109.46 %
0.327
A
Server: nginx
Date: Wed, 23 Feb 2022 14:43:51 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://cn2.8989898.xyz/

• https://cn2.8989898.xyz/
93.179.118.246
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0
5.763
A
small visible content (num chars: 0)
Server: nginx
Date: Wed, 23 Feb 2022 14:43:51 GMT
Content-Type: text/html
Last-Modified: Wed, 23 Feb 2022 14:42:48 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"621647e8-73"
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Content-Encoding: gzip

• http://cn2.8989898.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
93.179.118.246
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
https://cn2.8989898.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.46 %
Other inline scripts (∑/total): 0/0
0.350
A
Visible Content: 301 Moved Permanently nginx
Server: nginx
Date: Wed, 23 Feb 2022 14:43:58 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://cn2.8989898.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://cn2.8989898.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.61 %
Other inline scripts (∑/total): 0/0
5.923
A
Not Found
Visible Content: 404 Not Found nginx
Server: nginx
Date: Wed, 23 Feb 2022 14:44:03 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Content-Encoding: gzip

• https://93.179.118.246/
93.179.118.246
301
https://cn2.8989898.xyz/
Html is minified: 109.46 %
3.750
N
Certificate error: RemoteCertificateNameMismatch
Server: nginx
Date: Wed, 23 Feb 2022 14:43:59 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://cn2.8989898.xyz/

 

7. Comments


1. General Results, most used to calculate the result

Aname "cn2.8989898.xyz" is subdomain, public suffix is ".xyz", top-level-domain is ".xyz", top-level-domain-type is "generic", tld-manager is "XYZ.COM LLC", num .xyz-domains preloaded: 1186 (complete: 175327)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: cn2.8989898.xyz 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: cn2.8989898.xyz 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://93.179.118.246/ 93.179.118.246
301
https://cn2.8989898.xyz/
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: HSTS has preload directive
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
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):0 complete Content-Type - header (2 urls)
https://cn2.8989898.xyz/ 93.179.118.246


Url with incomplete Content-Type - header - missing charset
https://cn2.8989898.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


Url with incomplete Content-Type - header - missing charset
Ahttp://cn2.8989898.xyz/ 93.179.118.246
301
https://cn2.8989898.xyz/
Correct redirect http - https with the same domain name
Nhttps://93.179.118.246/ 93.179.118.246
301
https://cn2.8989898.xyz/
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 cn2.8989898.xyz, 1 ip addresses, 1 different http results.

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


3. DNS- and NameServer - Checks

AInfo:: 22 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 22 Queries complete, 22 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 11.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in Delegation: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: dns1.registrar-servers.com, dns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: dns1.registrar-servers.com.
AGood: Only one SOA.Primary Name Server found.: dns1.registrar-servers.com.
AGood: SOA.Primary Name Server included in the delegation set.: dns1.registrar-servers.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: dns1.registrar-servers.com, dns2.registrar-servers.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
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: registrar-servers.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
A
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2610:, 1 different subnets (first two blocks): 2610:00a1:, 2 different subnets (first three blocks): 2610:00a1:1024:, 2610:00a1:1025:, 2 different subnets (first four blocks): 2610:00a1:1024:0000:, 2610:00a1:1025:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: dns1.registrar-servers.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.
Nameserver doesn't pass all EDNS-Checks: ns0.centralnic.net: 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
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates

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: No https + http status 200 with inline CSS / JavaScript found
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
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
https://cn2.8989898.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
5.923 seconds
Warning: 404 needs more then one second
ADuration: 77850 milliseconds, 77.850 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
cn2.8989898.xyz
93.179.118.246
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
supported
ok
cn2.8989898.xyz
93.179.118.246
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
supported
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=cn2.8989898.xyz


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


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


cn2.8989898.xyz
cn2.8989898.xyz
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
supported
ok

cn2.8989898.xyz
cn2.8989898.xyz
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
supported
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=cn2.8989898.xyz


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


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


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

93.179.118.246
93.179.118.246
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0

 

9. Certificates

1.
1.
CN=cn2.8989898.xyz
11.02.2022
12.05.2022
937 days expired
cn2.8989898.xyz - 1 entry
1.
1.
CN=cn2.8989898.xyz
11.02.2022

12.05.2022
937 days expired


cn2.8989898.xyz - 1 entry

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0456F595E0500404CF4D749A038090B15523
Thumbprint:07F1BDA119F6F577D0693AA6B48AA2069F344808
SHA256 / Certificate:WxZ6Be+e9njBqlE0L0xqYoEs9qmfOk8Eysk+iR1rdU4=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):f0164ff274b6c0639f4c98ac8570f911b983fc221f651440a649a4f691fc9dd7
SHA256 hex / Subject Public Key Information (SPKI):f0164ff274b6c0639f4c98ac8570f911b983fc221f651440a649a4f691fc9dd7 (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 285 days


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

15.09.2025
expires in 285 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 3834 days


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

04.06.2035
expires in 3834 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


Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://cn2.8989898.xyz/
93.179.118.246
meta
other
1

0


0
0
0

 

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://cn2.8989898.xyz/
93.179.118.246
meta
content-type
text\/html; charset=utf-8


1
ok














 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns1.registrar-servers.com, dns2.registrar-servers.com

 

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

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
dns1.registrar-servers.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org

Answer: edns1.registrar-servers.com
2001:41d0:800:2d2c::2, 51.89.217.44

Answer: edns2.registrar-servers.com
2607:5300:203:7f53::2, 51.222.46.83

Answer: edns4.ultradns.com
2001:502:f3ff::204, 204.74.66.4
3
dns2.registrar-servers.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org

Answer: edns1.registrar-servers.com
2001:41d0:800:2d2c::2, 51.89.217.44

Answer: edns2.registrar-servers.com
2607:5300:203:7f53::2, 51.222.46.83

Answer: edns4.ultradns.com
2001:502:f3ff::204, 204.74.66.4
4
net
NS
k.root-servers.net (2001:7fd::1)

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
edns4.ultradns.net
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org

Answer: pdns196.ultradns.net
156.154.65.196, 2610:a1:1014::e8
6
org
NS
l.root-servers.net (2001:500:9f::42)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
7
edns4.ultradns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org

Answer: pdns196.ultradns.org
156.154.67.196, 2001:502:4612::e8
8
biz
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, w.gtld.biz, x.gtld.biz, y.gtld.biz
9
pdns196.ultradns.biz: 156.154.66.196, 2610:a1:1015::e8
NS
a.gtld.biz (2001:502:ad09::30)
10
uk
NS
m.root-servers.net (2001:dc3::35)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
11
pdns196.ultradns.co.uk: 156.154.69.196, 2610:a1:1017::e8
NS
dns1.nic.uk (2a01:618:400::1)
12
pdns196.ultradns.com: 156.154.64.196, 2001:502:f3ff::e8
NS
a.gtld-servers.net (2001:503:a83e::2:30)
13
info
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
14
pdns196.ultradns.info: 156.154.68.196, 2610:a1:1016::e8
NS
a0.info.afilias-nst.info (2001:500:19::1)
15
edns4.ultradns.net: 204.74.110.4
A
pdns196.ultradns.biz (2610:a1:1015::e8)
16
edns4.ultradns.net: 2610:a1:1014::204
AAAA
pdns196.ultradns.biz (2610:a1:1015::e8)
17
edns4.ultradns.org: 204.74.111.4
A
pdns196.ultradns.biz (2610:a1:1015::e8)
18
edns4.ultradns.org: 2001:502:4612::204
AAAA
pdns196.ultradns.biz (2610:a1:1015::e8)
19
dns1.registrar-servers.com: 156.154.132.200
A
edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
20
dns1.registrar-servers.com: 2610:a1:1024::200
AAAA
edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
21
dns2.registrar-servers.com: 156.154.133.200
A
edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
22
dns2.registrar-servers.com: 2610:a1:1025::200
AAAA
edns1.registrar-servers.com (2001:41d0:800:2d2c::2)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
cn2.8989898.xyz
5
issue
letsencrypt.org
1
0
8989898.xyz
0

no CAA entry found
1
0
xyz
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
8989898.xyz
v=spf1 include:spf.efwd.registrar-servers.com ~all
ok
1
0
cn2.8989898.xyz

ok
1
0
_acme-challenge.cn2.8989898.xyz

Name Error - The domain name does not exist
1
0
_acme-challenge.cn2.8989898.xyz.8989898.xyz

Name Error - The domain name does not exist
1
0
_acme-challenge.cn2.8989898.xyz.cn2.8989898.xyz

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
cn2.8989898.xyz
93.179.118.246
21
FTP



cn2.8989898.xyz
93.179.118.246
21
FTP



cn2.8989898.xyz
93.179.118.246
22
SSH



cn2.8989898.xyz
93.179.118.246
22
SSH



cn2.8989898.xyz
93.179.118.246
25
SMTP



cn2.8989898.xyz
93.179.118.246
25
SMTP



cn2.8989898.xyz
93.179.118.246
53
DNS



cn2.8989898.xyz
93.179.118.246
53
DNS



cn2.8989898.xyz
93.179.118.246
110
POP3



cn2.8989898.xyz
93.179.118.246
110
POP3



cn2.8989898.xyz
93.179.118.246
143
IMAP



cn2.8989898.xyz
93.179.118.246
143
IMAP



cn2.8989898.xyz
93.179.118.246
465
SMTP (encrypted)



cn2.8989898.xyz
93.179.118.246
465
SMTP (encrypted)



cn2.8989898.xyz
93.179.118.246
587
SMTP (encrypted, submission)



cn2.8989898.xyz
93.179.118.246
587
SMTP (encrypted, submission)



cn2.8989898.xyz
93.179.118.246
993
IMAP (encrypted)



cn2.8989898.xyz
93.179.118.246
993
IMAP (encrypted)



cn2.8989898.xyz
93.179.118.246
995
POP3 (encrypted)



cn2.8989898.xyz
93.179.118.246
995
POP3 (encrypted)



cn2.8989898.xyz
93.179.118.246
1433
MS SQL



cn2.8989898.xyz
93.179.118.246
1433
MS SQL



cn2.8989898.xyz
93.179.118.246
2082
cPanel (http)



cn2.8989898.xyz
93.179.118.246
2082
cPanel (http)



cn2.8989898.xyz
93.179.118.246
2083
cPanel (https)



cn2.8989898.xyz
93.179.118.246
2083
cPanel (https)



cn2.8989898.xyz
93.179.118.246
2086
WHM (http)



cn2.8989898.xyz
93.179.118.246
2086
WHM (http)



cn2.8989898.xyz
93.179.118.246
2087
WHM (https)



cn2.8989898.xyz
93.179.118.246
2087
WHM (https)



cn2.8989898.xyz
93.179.118.246
2089
cPanel Licensing



cn2.8989898.xyz
93.179.118.246
2089
cPanel Licensing



cn2.8989898.xyz
93.179.118.246
2095
cPanel Webmail (http)



cn2.8989898.xyz
93.179.118.246
2095
cPanel Webmail (http)



cn2.8989898.xyz
93.179.118.246
2096
cPanel Webmail (https)



cn2.8989898.xyz
93.179.118.246
2096
cPanel Webmail (https)



cn2.8989898.xyz
93.179.118.246
2222
DirectAdmin (http)



cn2.8989898.xyz
93.179.118.246
2222
DirectAdmin (http)



cn2.8989898.xyz
93.179.118.246
2222
DirectAdmin (https)



cn2.8989898.xyz
93.179.118.246
2222
DirectAdmin (https)



cn2.8989898.xyz
93.179.118.246
3306
mySql



cn2.8989898.xyz
93.179.118.246
3306
mySql



cn2.8989898.xyz
93.179.118.246
5224
Plesk Licensing



cn2.8989898.xyz
93.179.118.246
5224
Plesk Licensing



cn2.8989898.xyz
93.179.118.246
5432
PostgreSQL



cn2.8989898.xyz
93.179.118.246
5432
PostgreSQL



cn2.8989898.xyz
93.179.118.246
8080
Ookla Speedtest (http)



cn2.8989898.xyz
93.179.118.246
8080
Ookla Speedtest (http)



cn2.8989898.xyz
93.179.118.246
8080
Ookla Speedtest (https)



cn2.8989898.xyz
93.179.118.246
8080
Ookla Speedtest (https)



cn2.8989898.xyz
93.179.118.246
8083
VestaCP http



cn2.8989898.xyz
93.179.118.246
8083
VestaCP http



cn2.8989898.xyz
93.179.118.246
8083
VestaCP https



cn2.8989898.xyz
93.179.118.246
8083
VestaCP https



cn2.8989898.xyz
93.179.118.246
8443
Plesk Administration (https)



cn2.8989898.xyz
93.179.118.246
8443
Plesk Administration (https)



cn2.8989898.xyz
93.179.118.246
8447
Plesk Installer + Updates



cn2.8989898.xyz
93.179.118.246
8447
Plesk Installer + Updates



cn2.8989898.xyz
93.179.118.246
8880
Plesk Administration (http)



cn2.8989898.xyz
93.179.118.246
8880
Plesk Administration (http)



cn2.8989898.xyz
93.179.118.246
10000
Webmin (http)



cn2.8989898.xyz
93.179.118.246
10000
Webmin (http)



cn2.8989898.xyz
93.179.118.246
10000
Webmin (https)



cn2.8989898.xyz
93.179.118.246
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=bdf6723e-9f1d-4926-8885-bbb5086ba5fb

 

Last Result: https://check-your-website.server-daten.de/?q=cn2.8989898.xyz - 2022-02-23 15:43:22

 

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

 

<a href="https://check-your-website.server-daten.de/?q=cn2.8989898.xyz" target="_blank">Check this Site: cn2.8989898.xyz</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=cn2.8989898.xyz