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



V

Connect failure - perhaps firewall

Checked:
10.06.2021 23:10:55


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
grizzlynet.tplinkdns.com

Not Implemented
yes
1
0
www.grizzlynet.tplinkdns.com

Not Implemented
yes
1
0
grizzlynet.tplinkdns.com
A
71.193.251.81
Salem/Oregon/United States (US) - Comcast Cable Communications, LLC
No Hostname found
no



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 14631, 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: 01.07.2021, 00:00:00 +, Signature-Inception: 10.06.2021, 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: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.06.2021, 17:00:00 +, Signature-Inception: 10.06.2021, 16:00:00 +, KeyTag 14631, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 54714, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.06.2021, 18:24:21 +, Signature-Inception: 09.06.2021, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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

Zone: tplinkdns.com
tplinkdns.com
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 "gop4645jcajo73m8fedue7idr27pkdc6" between the hashed NSEC3-owner "gop426hgugeao6mrfmtkd10l4i5drclh" and the hashed NextOwner "gop4hjn75fgts89jjqplp3uci99c5d4b". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner gop426hgugeao6mrfmtkd10l4i5drclh.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 15.06.2021, 04:51:18 +, Signature-Inception: 08.06.2021, 03:41:18 +, KeyTag 54714, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "tplinkdns.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 17.06.2021, 04:24:04 +, Signature-Inception: 10.06.2021, 03:14:04 +, KeyTag 54714, Signer-Name: com



0 DNSKEY RR found




Zone: grizzlynet.tplinkdns.com
grizzlynet.tplinkdns.com
0 DS RR in the parent zone found

Zone: www.grizzlynet.tplinkdns.com
www.grizzlynet.tplinkdns.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
tplinkdns.com
U  ns1.tplinkdns.com
52.204.177.89
Ashburn/Virginia/United States (US) - Amazon.com, Inc.


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

com
  a.gtld-servers.net / nnn1-fra6


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-fra6


  d.gtld-servers.net / nnn1-fra6


  e.gtld-servers.net / nnn1-fra6


  f.gtld-servers.net / nnn1-lon6


  g.gtld-servers.net / nnn1-lon6


  h.gtld-servers.net / nnn1-lon6


  i.gtld-servers.net / nnn1-lon6


  j.gtld-servers.net / nnn1-ein2


  k.gtld-servers.net / nnn1-ein5


  l.gtld-servers.net / nnn1-ein4


  m.gtld-servers.net / nnn1-ein3


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1623359433
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:10


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1623359448
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:3


Domain:tplinkdns.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


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://grizzlynet.tplinkdns.com/
71.193.251.81 GZip used - 2574 / 7019 - 63.33 %
200

Html is minified: 145.80 %
0.580
H
small visible content (num chars: 114)
Chicken Coop Attendant ☰ SETTINGS INSTRUCTIONS LIVE VIDEO SYSTEM ABOUT CCA Version 3.0.0 Main Device Control
Date: Thu, 10 Jun 2021 21:11:42 GMT
Server: Apache/2.4.38 (Raspbian)
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 2574
Connection: close
Content-Type: text/html; charset=UTF-8

• https://grizzlynet.tplinkdns.com/
71.193.251.81
-2

1.570
V
ConnectFailure - Unable to connect to the remote server

• http://grizzlynet.tplinkdns.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
71.193.251.81
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.370
A
Not Found
Visible Content: Not Found The requested URL was not found on this server. Apache/2.4.38 (Raspbian) Server at grizzlynet.tplinkdns.com Port 80
Date: Thu, 10 Jun 2021 21:11:44 GMT
Server: Apache/2.4.38 (Raspbian)
Content-Length: 288
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://71.193.251.81/
71.193.251.81
-2

1.534
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "grizzlynet.tplinkdns.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 57967 (complete: 151507)
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
Agood - only one version with Http-Status 200
AGood: No cookie sent via http.
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct 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.
Vhttps://grizzlynet.tplinkdns.com/ 71.193.251.81
-2

connect failure - perhaps firewall
Vhttps://71.193.251.81/ 71.193.251.81
-2

connect failure - perhaps firewall
XFatal error: Nameserver doesn't support TCP connection: ns1.tplinkdns.com / 52.204.177.89: 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.204.177.89:53
XFatal error: Nameserver doesn't support TCP connection: ns2.tplinkdns.com / 54.87.217.253: 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.87.217.253:53
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns1.tplinkdns.com / 52.204.177.89
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns2.tplinkdns.com / 54.87.217.253

2. DNS- and NameServer - Checks

A
A
AInfo:: 13 different Name Servers found: 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, 13 Name Servers included in Delegation: 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, 13 Name Servers included in 1 Zone definitions: 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, 1 Name Servers listed in SOA.Primary: a.gtld-servers.net.
AGood: Only one SOA.Primary Name Server found.: a.gtld-servers.net.
AGood: SOA.Primary Name Server included in the delegation set.: a.gtld-servers.net.
AGood: All Name Server Domain Names have a Public Suffix.
A
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.tplinkdns.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.tplinkdns.com
Nameserver doesn't pass all EDNS-Checks: ns1.tplinkdns.com / 52.204.177.89: 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.tplinkdns.com / 54.87.217.253: 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

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.
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: 68860 milliseconds, 68.860 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

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


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
tplinkdns.com
-4

Not Implemented - The name server does not support the requested kind of query
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tplinkdns.com

Not Implemented - The name server does not support the requested kind of query
1
0
_acme-challenge.grizzlynet.tplinkdns.com.tplinkdns.com

Not Implemented - The name server does not support the requested kind of query
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=455247ca-e7d4-4b70-9f0d-e972beceee7b


Last Result: https://check-your-website.server-daten.de/?q=grizzlynet.tplinkdns.com - 2021-06-10 23:13:21


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

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