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

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


	1 RRSIG RR to validate DNSKEY RR found


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


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.05.2020, 17:00:00 +, Signature-Inception: 18.05.2020, 16: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 30909, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 39844, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


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


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


	• 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 "gop4570oled6i294ebvur7q3hvsnv5da" and the hashed NextOwner "gop4g541a6pf93tl4391hkospvddmmlu". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner gop4570oled6i294ebvur7q3hvsnv5da.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 22.05.2020, 06:04:32 +, Signature-Inception: 15.05.2020, 04:54:32 +, KeyTag 39844, Signer-Name: com


	0 DNSKEY RR found




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

3. Name Servers

Domain	Nameserver	NS-IP
www.tplinkdns.com	•
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.com, Inc.
com	• 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		•

4. SOA-Entries

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

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

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

Domain:	www.tplinkdns.com
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

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "tplinkdns.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
X	Fatal error: Nameserver isn't defined or has timeout
X	Fatal 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
X	Fatal 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
X	Fatal 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
X	Fatal 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
A	Info:: 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.
A	Good: Only one SOA.Primary Name Server found.: a.gtld-servers.net.
A	Good: SOA.Primary Name Server included in the delegation set.: a.gtld-servers.net.
A	Good: All Name Server Domain Names have a Public Suffix.
	Error: Name Server Domain Names with Public Suffix and without ip address found.: 13 Name Servers without ipv4 and ipv6: 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
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: gtld-servers.net
A
X	Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.tplinkdns.com
X	Fatal 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.
A	Good: 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
A	Info: No img element found, no alt attribute checked
A	Good: 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
A	Duration: 44206 milliseconds, 44.206 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

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
tplinkdns.com				2	0
com	0		no CAA entry found	1	0

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries	∑ Timeout
tplinkdns.com			2	0
_acme-challenge.tplinkdns.com			2	0
_acme-challenge.tplinkdns.com.tplinkdns.com			2	0

15. Portchecks

No Port checks

Permalink: https://check-your-website.server-daten.de/?i=1f91026e-5318-4abf-8b18-88335e3c2ba9

Last Result: https://check-your-website.server-daten.de/?q=tplinkdns.com - 2020-08-04 11:28:18

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

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