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

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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 5613, Flags 256


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


	Public Key with Algorithm 8, KeyTag 30903, 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.2024, 00:00:00 +, Signature-Inception: 01.04.2024, 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 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.04.2024, 05:00:00 +, Signature-Inception: 01.04.2024, 04:00:00 +, KeyTag 5613, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 4534, Flags 256


	Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.04.2024, 14:02:35 +, Signature-Inception: 28.03.2024, 13:57:35 +, KeyTag 19718, Signer-Name: com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19718 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest "isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=" 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 "gop4nu2eusucqq3rfdrkqrgrlvvhnagp". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner gop426hgugeao6mrfmtkd10l4i5drclh.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.04.2024, 05:41:13 +, Signature-Inception: 01.04.2024, 04:31:13 +, KeyTag 4534, 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 "ck0q2d6ni4i7eqh8na30ns61o48ul8g5". 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: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 06.04.2024, 04:24:49 +, Signature-Inception: 30.03.2024, 03:14:49 +, KeyTag 4534, Signer-Name: com


	0 DNSKEY RR found




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

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

3. Name Servers

Domain	Nameserver
tplinkdns.com	• ns1.tplinkdns.com
	• ns2.tplinkdns.com
com	• a.gtld-servers.net / nnn1-defra-5	•
	• b.gtld-servers.net / nnn1-eltxl1	•
	• c.gtld-servers.net / nnn1-defra-5	•
	• d.gtld-servers.net / nnn1-defra-5	•
	• e.gtld-servers.net / nnn1-defra-5	•
	• f.gtld-servers.net / nnn1-defra-4	•
	• g.gtld-servers.net / nnn1-defra-4	•
	• h.gtld-servers.net / nnn1-defra-4	•
	• i.gtld-servers.net / nnn1-defra-4	•
	• j.gtld-servers.net / nnn1-ein1	•
	• k.gtld-servers.net / nnn1-nlams-2e	•
	• l.gtld-servers.net / nnn1-ein1	•
	• m.gtld-servers.net / nnn1-ein1	•

4. SOA-Entries

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1711992268
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:	1711992283
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

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 "ruyfam.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: 93017 (complete: 240622)
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "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.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.ruyfam.tplinkdns.com
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
U		No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. 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.
A
	Nameserver doesn't pass all EDNS-Checks: ns1.tplinkdns.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: ns2.tplinkdns.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.
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.
	4. Content- and Performance-critical Checks
	Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 283370 milliseconds, 283.370 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" > of the last months 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. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

13. Nameserver - IP-Adresses

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

No NameServer - IP address - Informations found

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
tplinkdns.com	-3		Name Error - The domain name does not exist	1	0
com	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries	∑ Timeout
tplinkdns.com		Name Error - The domain name does not exist	1	0
_acme-challenge.ruyfam.tplinkdns.com.tplinkdns.com		Name Error - The domain name does not exist	1	0

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=960fa8cb-6f18-402d-842d-7f6aff4e8fb8

Last Result: https://check-your-website.server-daten.de/?q=ruyfam.tplinkdns.com - 2024-04-01 19:24:58

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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

QR-Code of this page - https://check-your-website.server-daten.de/?d=ruyfam.tplinkdns.com