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



W

wrong Web-Response

Checked:
26.11.2019 14:28:24


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
y21.xyz
A
139.59.84.48
Bengaluru/Karnataka/India (IN) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA

yes


www.y21.xyz

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



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 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



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



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3505, Flags 256



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



Public Key with Algorithm 8, KeyTag 28065, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 06.12.2019, 11:02:39 +, Signature-Inception: 05.11.2019, 22:48:41 +, 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: y21.xyz
y21.xyz
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 "61r0k31bdur6pnra3ebcec0v17ti633v" between the hashed NSEC3-owner "61q7c8uapijs93h61n668vu729oqease" and the hashed NextOwner "61r8sitndb10on7sjtf6ed5n9ok4hhsp". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 61q7c8uapijs93h61n668vu729oqease.xyz., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.12.2019, 13:51:35 +, Signature-Inception: 07.11.2019, 01:03:26 +, KeyTag 28065, Signer-Name: xyz



0 DNSKEY RR found




Zone: www.y21.xyz
www.y21.xyz
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.y21.xyz
  ns1.digitalocean.com

y21.xyz
  ns1.digitalocean.com / 67m29
173.245.58.51
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3a33
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns2.digitalocean.com / 67m26
173.245.59.41
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3b29
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns3.digitalocean.com / 67m28
198.41.222.173
Newark/New Jersey/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::c629:dead
Columbus/North Carolina/United States (US) - CLOUDFLARE

xyz
  generationxyz.nic.xyz / NRDT-75SODK-AB8TIQ


  x.nic.xyz / NRDT-75SODK-AB8TIQ


  y.nic.xyz / FMCL-UEZCAO-YJSSPL


  z.nic.xyz / FMCL-UEZCAO-YJSSPL


4. SOA-Entries


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


Domain:y21.xyz
Zone-Name:
Primary:ns1.digitalocean.com
Mail:hostmaster.y21.xyz
Serial:1574771807
Refresh:10800
Retry:3600
Expire:604800
TTL:1800
num Entries:6


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


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://y21.xyz/
139.59.84.48 GZip used - 396 / 612 - 35.29 %
200

Html is minified: 129.94 %
0.313
H
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 26 Nov 2019 13:28:45 GMT
Content-Type: text/html
Last-Modified: Tue, 26 Nov 2019 11:31:51 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"5ddd0d27-264"
Content-Encoding: gzip

• https://y21.xyz/
139.59.84.48
-4

0.593
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• http://y21.xyz:443/
139.59.84.48
-3

0.587
A
ReceiveFailure - The underlying connection was closed: An unexpected error occurred on a receive.
Visible Content:

• http://y21.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
139.59.84.48 GZip used - 141 / 178 - 20.79 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 108.54 %
0.316
A
Not Found
Visible Content:
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 26 Nov 2019 13:28:46 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

7. Comments


1. General Results, most used to calculate the result

Aname "y21.xyz" is domain, public suffix is "xyz", top-level-domain-type is "generic", tld-manager is "XYZ.COM LLC"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood - only one version with Http-Status 200
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)
http://y21.xyz/ 139.59.84.48


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


Url with incomplete Content-Type - header - missing charset
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)


3. DNS- and NameServer - Checks

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: ns1.digitalocean.com,ns2.digitalocean.com,ns3.digitalocean.com
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.digitalocean.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: 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: 28903 milliseconds, 28.903 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


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

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
y21.xyz
0

no CAA entry found
1
0
xyz
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
y21.xyz

ok
1
0
_acme-challenge.y21.xyz

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

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=17d449af-9eba-40a8-a23b-1bbd1fd7bc61


Last Result: https://check-your-website.server-daten.de/?q=y21.xyz - 2019-11-26 15:16:02


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

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