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



T

Timeout

Checked:
08.04.2020 00:02:14


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
ards.dev
A
104.198.0.122
Ashburn/Virginia/United States (US) - Google LLC
Hostname: 122.0.198.104.bc.googleusercontent.com
yes
2
0

AAAA

yes


www.ards.dev
CNAME
ards.dev
yes
1
0

A
104.198.0.122
Ashburn/Virginia/United States (US) - Google LLC
Hostname: 122.0.198.104.bc.googleusercontent.com
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



Status: Valid because published



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 33853, Flags 256



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2020, 00:00:00 +, Signature-Inception: 01.04.2020, 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: dev
dev
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.04.2020, 21:00:00 +, Signature-Inception: 07.04.2020, 20:00:00 +, KeyTag 48903, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 61929, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 27.04.2020, 07:14:18 +, Signature-Inception: 05.04.2020, 07:14:18 +, KeyTag 60074, Signer-Name: dev



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



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

Zone: ards.dev
ards.dev
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 "rfgl5g88dq6edhthd0v2044k7n9mrpf5" between the hashed NSEC3-owner "rfgl5g88dq6edhthd0v2044k7n9mrpf5" and the hashed NextOwner "rfgoe0fr9o983qak6i0f4jkegp1b4heq". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner rfgl5g88dq6edhthd0v2044k7n9mrpf5.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 27.04.2020, 07:14:18 +, Signature-Inception: 05.04.2020, 07:14:18 +, KeyTag 61929, Signer-Name: dev



0 DNSKEY RR found




Zone: www.ards.dev
www.ards.dev
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
ards.dev
  ns-cloud-b1.googledomains.com
216.239.32.107
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:32::6b
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-b2.googledomains.com
216.239.34.107
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:34::6b
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-b3.googledomains.com
216.239.36.107
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:36::6b
Ashburn/Virginia/United States (US) - Google LLC


  ns-cloud-b4.googledomains.com
216.239.38.107
Alameda/California/United States (US) - Google LLC


 
2001:4860:4802:38::6b
Ashburn/Virginia/United States (US) - Google LLC

dev
  ns-tld1.charlestonroadregistry.com


  ns-tld2.charlestonroadregistry.com


  ns-tld3.charlestonroadregistry.com


  ns-tld4.charlestonroadregistry.com


  ns-tld5.charlestonroadregistry.com


4. SOA-Entries


Domain:dev
Zone-Name:
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:5


Domain:ards.dev
Zone-Name:
Primary:ns-cloud-b1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


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://ards.dev/
104.198.0.122
-14

10.033
T
Timeout - The operation has timed out

• http://www.ards.dev/
104.198.0.122
-14

10.037
T
Timeout - The operation has timed out

• https://ards.dev/
104.198.0.122
-14

10.033
T
Timeout - The operation has timed out

• https://www.ards.dev/
104.198.0.122
-14

10.043
T
Timeout - The operation has timed out

• http://ards.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
104.198.0.122
-14

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

• http://www.ards.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
104.198.0.122
-14

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

7. Comments


1. General Results, most used to calculate the result

Aname "ards.dev" is domain, public suffix is "dev", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc."
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
AExcellent: Domain is in the Google-Preload-List
AExcellent: Domain is in the Mozilla/Firefox-Preload-List
AHSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

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: ns-cloud-b1.googledomains.com,ns-cloud-b2.googledomains.com,ns-cloud-b3.googledomains.com,ns-cloud-b4.googledomains.com
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
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://ards.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.198.0.122
-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.ards.dev/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.198.0.122
-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.
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: 112580 milliseconds, 112.580 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)

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1544629623
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-06 15:13:08
2020-07-05 15:13:08
ards.dev, www.ards.dev - 2 entries



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

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2673978239
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-06 13:13:08
2020-07-05 13:13:08
ards.dev, www.ards.dev
2 entries



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
www.ards.dev



1
0
ards.dev
0

no CAA entry found
1
0
dev
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ards.dev

ok
1
0
www.ards.dev


1
0
_acme-challenge.ards.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.www.ards.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.ards.dev.ards.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.www.ards.dev.ards.dev

Name Error - The domain name does not exist
1
0
_acme-challenge.www.ards.dev.www.ards.dev

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=1a48ed89-e447-49b6-88aa-47c2fd77b00b


Last Result: https://check-your-website.server-daten.de/?q=ards.dev - 2020-04-08 00:02:14


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

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