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


Info: Problems with 3.048.289 Letsencrypt certificates (378.325 accounts). They must be revoked (revocation starts 2020-03-04 20:00 UTC) - see Revoking certain certificates on March 4. Update 2020-03-07: Good news: Mass-revocation is canceled.

This tool: A check (SerialNumber) is added. Letsencrypt has published a list of critical SerialNumbers, this list is checked. See the part "9. Certificates". If there is a warning, renew that certificate and replace the current certificate.




X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
02.12.2019 02:03:32


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
gcd.best
A
54.249.76.230
Tokyo/Japan (JP) - Amazon Technologies Inc.
Hostname: ec2-54-249-76-230.ap-northeast-1.compute.amazonaws.com
yes
1
0

AAAA

yes


www.gcd.best

Name Error
yes
1
0


2. DNSSEC

Info: The Xml-split has triggered some hidden bugs. Now it looks ok.
If root or the top level zone isn't validated, it's buggy.
Both green and your domain is red -> it's your domain.

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



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.12.2019, 00:00:00 +, Signature-Inception: 30.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: best
best
6 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.12.2019, 17:00:00 +, Signature-Inception: 01.12.2019, 16: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



9 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 10533, Flags 256



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



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



Public Key with Algorithm 8, KeyTag 32356, Flags 256



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



Public Key with Algorithm 8, KeyTag 48334, Flags 256



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



Public Key with Algorithm 8, KeyTag 53701, Flags 256



Public Key with Algorithm 8, KeyTag 64228, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 26.12.2019, 03:48:08 +, Signature-Inception: 25.11.2019, 23:43:24 +, KeyTag 41279, Signer-Name: best



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 41279, DigestType 1 and Digest "hR6dY0XBZEpx/0QC6Bi774QZcbI=" 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 41279, DigestType 2 and Digest "0MJmsUfp+nEiIVzMo2sj1DQHvS8DsuO26RfTULMapf0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: gcd.best
gcd.best
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.Bitmap: NS, DS, RRSIG



0 DNSKEY RR found





Zone: www.gcd.best
www.gcd.best
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.gcd.best
  ns1.dynadot.com

gcd.best
U  ns1.dynadot.com
35.160.240.86
Portland/Oregon/United States (US) - Amazon Technologies Inc.


U 
52.25.56.204
Portland/Oregon/United States (US) - Amazon.com, Inc.


U 
54.68.4.223
Portland/Oregon/United States (US) - Amazon.com, Inc.


U 
54.69.45.191
Portland/Oregon/United States (US) - Amazon.com, Inc.


U  ns2.dynadot.com
3.214.135.194
Ashburn/Virginia/United States (US) - Amazon Technologies Inc.


U 
3.218.93.94
Ashburn/Virginia/United States (US) - Amazon Technologies Inc.


U 
3.223.22.200
Ashburn/Virginia/United States (US) - Amazon Technologies Inc.


U 
3.224.5.165
Ashburn/Virginia/United States (US) - Amazon Technologies Inc.

best
  a.nic.best / NRDT-75SODK-AB8TIQ


  b.nic.best / FMCL-UEZCAO-YJSSPL


  c.nic.best / FMCL-UEZCAO-YJSSPL


  d.nic.best / NRDT-75SODK-AB8TIQ


4. SOA-Entries


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


Domain:gcd.best
Zone-Name:
Primary:ns1.dynadot.com
Mail:hostmaster.gcd.best
Serial:1575248503
Refresh:16384
Retry:2048
Expire:1048576
TTL:2560
num Entries:8


Domain:www.gcd.best
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://gcd.best/
54.249.76.230
-14

10.040
T
Timeout - The operation has timed out

• https://gcd.best/
54.249.76.230
-14

10.033
T
Timeout - The operation has timed out

• http://gcd.best/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
54.249.76.230
-14

10.056
T
Timeout - The operation has timed out
Visible Content:

7. Comments


1. General Results, most used to calculate the result

Aname "gcd.best" is domain, public suffix is "best", top-level-domain-type is "generic", tld-manager is "BestTLD Pty Ltd"
Agood: All ip addresses are public addresses
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.dynadot.com / 35.160.240.86: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 35.160.240.86:53
XFatal error: Nameserver doesn't support TCP connection: ns1.dynadot.com / 52.25.56.204: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 52.25.56.204:53
XFatal error: Nameserver doesn't support TCP connection: ns1.dynadot.com / 54.68.4.223: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 54.68.4.223:53
XFatal error: Nameserver doesn't support TCP connection: ns1.dynadot.com / 54.69.45.191: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 54.69.45.191:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynadot.com / 3.214.135.194: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 3.214.135.194:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynadot.com / 3.218.93.94: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 3.218.93.94:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynadot.com / 3.223.22.200: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 3.223.22.200:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynadot.com / 3.224.5.165: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 3.224.5.165:53

2. 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.dynadot.com,ns2.dynadot.com
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.dynadot.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.dynadot.com
Nameserver doesn't pass all EDNS-Checks: ns1.dynadot.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: ns1.dynadot.com / 35.160.240.86: 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: ns1.dynadot.com / 52.25.56.204: 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: ns1.dynadot.com / 54.68.4.223: 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: ns1.dynadot.com / 54.69.45.191: 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: ns2.dynadot.com / 3.214.135.194: 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: ns2.dynadot.com / 3.218.93.94: 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: ns2.dynadot.com / 3.223.22.200: 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: ns2.dynadot.com / 3.224.5.165: 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.

3. Content- and Performance-critical Checks

http://gcd.best/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 54.249.76.230
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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: 179320 milliseconds, 179.320 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)

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


11. Html-Content - Entries

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


12. Nameserver - IP-Adresses (alpha)

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
gcd.best
0

no CAA entry found
1
0
best
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
gcd.best

ok
1
0
_acme-challenge.gcd.best

Name Error - The domain name does not exist
1
0
_acme-challenge.gcd.best.gcd.best

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=2cfb0e87-38c7-4317-88c8-3aa64bb1e0a7


Last Result: https://check-your-website.server-daten.de/?q=gcd.best - 2019-12-02 02:03:32


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

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