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 20326, Flags 257 (SEP = Secure Entry Point)


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


	Public Key with Algorithm 8, KeyTag 61809, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 25307, DigestType 2 and Digest vAQS1ZgXQko0BAZ28a4SBbHzP8lRDn4wEUcRhR/87eQ=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner tl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.11.2025, 05:00:00 +, Signature-Inception: 06.11.2025, 04:00:00 +, KeyTag 61809, Signer-Name: (root)


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 25764, Flags 256


	Public Key with Algorithm 8, KeyTag 27606, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner tl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.11.2025, 00:00:00 +, Signature-Inception: 03.11.2025, 00:00:00 +, KeyTag 25307, Signer-Name: tl


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


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

Zone: ds.tl
ds.tl	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 "aum6i61knlp77apm7p1baf1ohl3okamg" between the hashed NSEC3-owner "9mpremg5vvsobbir7voshoss0vfgjiri" and the hashed NextOwner "damu868o2h6gombs1q5td1vfn40lksjq". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 9mpremg5vvsobbir7voshoss0vfgjiri.tl., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 12.11.2025, 20:00:00 +, Signature-Inception: 26.10.2025, 20:00:00 +, KeyTag 25764, Signer-Name: tl


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "uo137i5j43543o93jrv5gnph3099c14l" as Owner. That's the Hash of "tl" with the NextHashedOwnerName "1sjai8obtk1ant02d9e9fcmqksfa0a29". So that domain name is the Closest Encloser of "ds.tl". Opt-Out: True. Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner uo137i5j43543o93jrv5gnph3099c14l.tl., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 12.11.2025, 20:00:00 +, Signature-Inception: 26.10.2025, 20:00:00 +, KeyTag 25764, Signer-Name: tl


	The ClosestEncloser says, that "*.tl" with the Hash "jk0811bihhrccvjq8p94r5h9878snd8e" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "jem55urap4aq72idel64tnhmsqg6pfkf" and the Next Owner "kp6g5drthr9j8e6k95la7ugf6jd70loi", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner jem55urap4aq72idel64tnhmsqg6pfkf.tl., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 12.11.2025, 20:00:00 +, Signature-Inception: 26.10.2025, 20:00:00 +, KeyTag 25764, Signer-Name: tl

Zone: www.ds.tl
www.ds.tl	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 "bu4gq9tjus8hmhl3fc29v2megtm4mo7d" between the hashed NSEC3-owner "9mpremg5vvsobbir7voshoss0vfgjiri" and the hashed NextOwner "damu868o2h6gombs1q5td1vfn40lksjq". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 9mpremg5vvsobbir7voshoss0vfgjiri.tl., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 12.11.2025, 20:00:00 +, Signature-Inception: 26.10.2025, 20:00:00 +, KeyTag 25764, Signer-Name: tl


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "uo137i5j43543o93jrv5gnph3099c14l" as Owner. That's the Hash of "tl" with the NextHashedOwnerName "1sjai8obtk1ant02d9e9fcmqksfa0a29". So that domain name is the Closest Encloser of "www.ds.tl". Opt-Out: True. Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner uo137i5j43543o93jrv5gnph3099c14l.tl., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 12.11.2025, 20:00:00 +, Signature-Inception: 26.10.2025, 20:00:00 +, KeyTag 25764, Signer-Name: tl


	The ClosestEncloser says, that "*.tl" with the Hash "jk0811bihhrccvjq8p94r5h9878snd8e" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "jem55urap4aq72idel64tnhmsqg6pfkf" and the Next Owner "kp6g5drthr9j8e6k95la7ugf6jd70loi", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner jem55urap4aq72idel64tnhmsqg6pfkf.tl., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 12.11.2025, 20:00:00 +, Signature-Inception: 26.10.2025, 20:00:00 +, KeyTag 25764, Signer-Name: tl

3. Name Servers

Domain	Nameserver
www.ds.tl	• pch.nic.tl
ds.tl	• pch.nic.tl
tl	• ns.anycast.nic.tl / 13.fra.pch	•
	• ns1.anycastdns.cz	•
	• ns2.anycastdns.cz	•
	• pch.nic.tl

4. SOA-Entries

Domain:	tl
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	tl
Zone-Name:	tl
Primary:	pch.nic.tl
Mail:	hostmaster.coccaregistry.org
Serial:	2025110608
Refresh:	21600
Retry:	3600
Expire:	604800
TTL:	86400
num Entries:	3

Domain:	ds.tl
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	www.ds.tl
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 "ds.tl" is domain, public suffix is ".tl", top-level-domain is ".tl", top-level-domain-type is "country-code", Country is Timor-Leste, tld-manager is "Autoridade Nacional de Comunicações", num .tl-domains preloaded: 11 (complete: 276475)
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.ds.tl
	2. Header-Checks
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:: 4 different Name Servers found: ns.anycast.nic.tl, ns1.anycastdns.cz, ns2.anycastdns.cz, pch.nic.tl, 3 Name Servers included in Delegation: ns.anycast.nic.tl, ns1.anycastdns.cz, ns2.anycastdns.cz, 3 Name Servers included in 2 Zone definitions: ns.anycast.nic.tl, ns1.anycastdns.cz, ns2.anycastdns.cz, 1 Name Servers listed in SOA.Primary: pch.nic.tl.
A	Good: Only one SOA.Primary Name Server found.: pch.nic.tl.
	Error: SOA.Primary Name Server not included in the delegation set.: pch.nic.tl.
A	Good: All Name Server Domain Names have a Public Suffix.
A
A	Good: Nameserver supports TCP connections: 3 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 3 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: pch.nic.tl: 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: pch.nic.tl: 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: pch.nic.tl: 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: 28383 milliseconds, 28.383 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.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

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
tl	0		no CAA entry found	1	0

15. TXT - Entries

No TXT entries found

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=131f49eb-6fad-4cd1-9015-309d4bcc3ba3

Last Result: https://check-your-website.server-daten.de/?q=ds.tl%2Fhelp-third-party-plugins - 2025-11-06 16:38:27

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

<a href="https://check-your-website.server-daten.de/?q=ds.tl%2Fhelp-third-party-plugins" target="_blank">Check this Site: ds.tl%2Fhelp-third-party-plugins</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=ds.tl/help-third-party-plugins