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:
11.09.2019 06:52:35


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
deersg.duckdns.org


yes
3
3
www.deersg.duckdns.org


yes
3
3
deersg.duckdns.org
A
116.86.8.127
Mei Hwan//Singapore (SG) - SGCABLEVISION
No Hostname found
no


www.deersg.duckdns.org
A
116.86.8.127
Mei Hwan//Singapore (SG) - SGCABLEVISION
No Hostname found
no



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2019, 00:00:00 +, Signature-Inception: 09.09.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: org
org
2 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: 23.09.2019, 20:00:00 +, Signature-Inception: 10.09.2019, 19:00:00 +, KeyTag 59944, Signer-Name: (root)



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



4 DNSKEY RR found



Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 36752, Flags 256



Public Key with Algorithm 7, KeyTag 47612, Flags 256



3 RRSIG RR to validate DNSKEY RR found



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.09.2019, 15:29:21 +, Signature-Inception: 09.09.2019, 14:29:21 +, KeyTag 9795, Signer-Name: org



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.09.2019, 15:29:21 +, Signature-Inception: 09.09.2019, 14:29:21 +, KeyTag 17883, Signer-Name: org



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.09.2019, 15:29:21 +, Signature-Inception: 09.09.2019, 14:29:21 +, KeyTag 47612, Signer-Name: org



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 47612 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 1 and Digest "Nk36s9ryVMq0d7VnWxB2bdqiSYI=" 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 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: duckdns.org
duckdns.org
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: deersg.duckdns.org
deersg.duckdns.org
0 DS RR in the parent zone found



0 DNSKEY RR found





Zone: www.deersg.duckdns.org
www.deersg.duckdns.org
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.deersg.duckdns.org
 

deersg.duckdns.org
U  ns1.duckdns.org
54.187.92.222
Portland/Oregon/United States (US) - Amazon Technologies Inc.


  ns2.duckdns.org


U  ns3.duckdns.org
52.26.169.94
Portland/Oregon/United States (US) - Amazon.com, Inc.

duckdns.org
U  ns1.duckdns.org


U  ns2.duckdns.org


U  ns3.duckdns.org

org
  a0.org.afilias-nst.info / ns000a.app2.mia2.afilias-nst.info


  a2.org.afilias-nst.info / 2.ber.pch


  b0.org.afilias-nst.org / ns000b.app7.ams2.afilias-nst.info


  b2.org.afilias-nst.org / 5.fra.pch


  c0.org.afilias-nst.info / ns000b.app26.ams2.afilias-nst.info


  d0.org.afilias-nst.org / app9.iad1.hosts.meta.redstone.afilias-nst.info-2


4. SOA-Entries


Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013622654
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:duckdns.org
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:3


Domain:deersg.duckdns.org
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:deersg.duckdns.org
Zone-Name:
Primary:ns1.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:deersg.duckdns.org
Zone-Name:
Primary:ns3.duckdns.org
Mail:hostmaster.duckdns.org
Serial:2019170803
Refresh:6000
Retry:120
Expire:2419200
TTL:600
num Entries:1


Domain:www.deersg.duckdns.org
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://deersg.duckdns.org/
116.86.8.127
-14

10.013
T
Timeout - The operation has timed out

• http://www.deersg.duckdns.org/
116.86.8.127
-14

10.010
T
Timeout - The operation has timed out

• https://deersg.duckdns.org/
116.86.8.127
-2

1.577
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 116.86.8.127:443

• https://www.deersg.duckdns.org/
116.86.8.127
-2

1.580
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 116.86.8.127:443

• http://deersg.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
116.86.8.127
-14

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

• http://www.deersg.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
116.86.8.127
-14

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

7. Comments


1. General Results, most used to calculate the result

Aname "deersg.duckdns.org" is domain, public suffix is "duckdns.org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
Agood: All ip addresses are public addresses
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Vhttps://deersg.duckdns.org/ 116.86.8.127
-2

connect failure - perhaps firewall
Vhttps://www.deersg.duckdns.org/ 116.86.8.127
-2

connect failure - perhaps firewall
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 54.187.92.222:53
XFatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org / 54.187.92.222: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 54.187.92.222:53
XFatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 54.191.117.119:53
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 52.26.169.94:53
XFatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org / 52.26.169.94: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 52.26.169.94:53

2. DNS- and NameServer - Checks

XNameserver Timeout checking Echo Capitalization: ns1.duckdns.org
XNameserver Timeout checking Echo Capitalization: ns1.duckdns.org / 54.187.92.222
XNameserver Timeout checking Echo Capitalization: ns2.duckdns.org
XNameserver Timeout checking Echo Capitalization: ns3.duckdns.org / 52.26.169.94
XNameserver Timeout checking EDNS512: ns3.duckdns.org
XNameserver Timeout checking EDNS512: ns3.duckdns.org / 52.26.169.94

Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org / 54.187.92.222: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: 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.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 52.26.169.94: OP100: fatal timeout. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
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://deersg.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.86.8.127
-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.
http://www.deersg.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.86.8.127
-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: 281264 milliseconds, 281.264 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
deersg.duckdns.org



3
3
duckdns.org



3
3
org
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
deersg.duckdns.org


3
3
_acme-challenge.deersg.duckdns.org


3
3
_acme-challenge.deersg.duckdns.org.deersg.duckdns.org


3
3


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=090245e0-b477-43b1-ab05-7c18973c2658


Last Result: https://check-your-website.server-daten.de/?q=deersg.duckdns.org - 2019-09-11 06:52:35


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

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