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


	Public Key with Algorithm 8, KeyTag 61050, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 51676, DigestType 2 and Digest iDF19vXGjqgVY7YtGyt5tqmX1g3G4gzHCv0M1rfoL2I=


	DS with Algorithm 8, KeyTag 51974, DigestType 2 and Digest oG3EdFfMEYXPGzp89uzLhJeN6Sk53Rgr7tlSFQnQ2ns=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.01.2025, 05:00:00 +, Signature-Inception: 03.01.2025, 04:00:00 +, KeyTag 26470, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 24654, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 01.02.2025, 09:06:56 +, Signature-Inception: 02.01.2025, 07:36:56 +, KeyTag 51974, Signer-Name: site


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


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

Zone: stoff81.site
stoff81.site	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 "c921pvif88abs8ahnnm8160jkoghn20d" between the hashed NSEC3-owner "c91csoiv0sn9pd4numv8epa2i99dtjua" and the hashed NextOwner "c92olqftgkfr7mt3vvkvfu2m5ab81d1m". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner c91csoiv0sn9pd4numv8epa2i99dtjua.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 22.01.2025, 17:52:38 +, Signature-Inception: 23.12.2024, 16:22:38 +, KeyTag 24654, Signer-Name: site


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "kkkldpnn5k2662ei72hm1tvtee3uakea" as Owner. That's the Hash of "site" with the NextHashedOwnerName "kkletpllcs8l9v4016d5lhccgrim8hq6". So that domain name is the Closest Encloser of "stoff81.site". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner kkkldpnn5k2662ei72hm1tvtee3uakea.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2025, 09:06:56 +, Signature-Inception: 02.01.2025, 07:36:56 +, KeyTag 24654, Signer-Name: site


	The ClosestEncloser says, that "*.site" with the Hash "l8ao6no1n0ps66vuqcd9k3m8k0qnrg95" 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 "l8an91mkqp10hpd6194dtl5qcvn50kug" and the Next Owner "l8e70aeq0ef0aaglgega96drq52a2a5a", 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 l8an91mkqp10hpd6194dtl5qcvn50kug.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2025, 16:20:39 +, Signature-Inception: 02.01.2025, 14:50:39 +, KeyTag 24654, Signer-Name: site

Zone: www.stoff81.site
www.stoff81.site	0 DS RR in the parent zone found


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "kkkldpnn5k2662ei72hm1tvtee3uakea" as Owner. That's the Hash of "site" with the NextHashedOwnerName "kkletpllcs8l9v4016d5lhccgrim8hq6". So that domain name is the Closest Encloser of "www.stoff81.site". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner kkkldpnn5k2662ei72hm1tvtee3uakea.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2025, 09:06:56 +, Signature-Inception: 02.01.2025, 07:36:56 +, KeyTag 24654, Signer-Name: site


	The ClosestEncloser says, that "*.site" with the Hash "l8ao6no1n0ps66vuqcd9k3m8k0qnrg95" 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 "l8an91mkqp10hpd6194dtl5qcvn50kug" and the Next Owner "l8e70aeq0ef0aaglgega96drq52a2a5a", 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 l8an91mkqp10hpd6194dtl5qcvn50kug.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 01.02.2025, 16:20:39 +, Signature-Inception: 02.01.2025, 14:50:39 +, KeyTag 24654, Signer-Name: site

3. Name Servers

Domain	Nameserver
www.stoff81.site	• ns0.centralnic.net
stoff81.site	• ns0.centralnic.net
site	• a.nic.site	•
	• b.nic.site	•
	• e.nic.site	•
	• f.nic.site	•
	• ns0.centralnic.net

4. SOA-Entries

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

Domain:	site
Zone-Name:	site
Primary:	ns0.centralnic.net
Mail:	hostmaster.centralnic.net
Serial:	392004
Refresh:	900
Retry:	1800
Expire:	6048000
TTL:	3600
num Entries:	4

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

Domain:	www.stoff81.site
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 "stoff81.site" is domain, public suffix is ".site", top-level-domain is ".site", top-level-domain-type is "generic", tld-manager is "DotSite Inc.", num .site-domains preloaded: 332 (complete: 263653)
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.stoff81.site
	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:: 5 different Name Servers found: a.nic.site, b.nic.site, e.nic.site, f.nic.site, ns0.centralnic.net, 4 Name Servers included in Delegation: a.nic.site, b.nic.site, e.nic.site, f.nic.site, 4 Name Servers included in 2 Zone definitions: a.nic.site, b.nic.site, e.nic.site, f.nic.site, 1 Name Servers listed in SOA.Primary: ns0.centralnic.net.
A	Good: Only one SOA.Primary Name Server found.: ns0.centralnic.net.
	Error: SOA.Primary Name Server not included in the delegation set.: ns0.centralnic.net.
A	Good: All Name Server Domain Names have a Public Suffix.
A
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
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: 54753 milliseconds, 54.753 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)

Issuer				last 7 days	active	num Certs
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2				0	1	1
CN=R11, O=Let's Encrypt, C=US				0	0	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
7788131950 leaf cert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2024-07-24 18:16:56	2025-07-24 18:16:56	stoff81.site - 1 entries
7752870759 leaf cert	CN=R11, O=Let's Encrypt, C=US	2024-07-19 23:46:51	2024-10-17 23:46:50	stoff81.site, www.stoff81.site - 2 entries

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

Issuer				last 7 days	active	num Certs
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2				0	1	1
CN=R11, O=Let's Encrypt, C=US				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
13869433848 leaf cert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2024-07-24 16:16:56	2025-07-24 16:16:56	stoff81.site 1 entries
13857927397 leaf cert	CN=R11, O=Let's Encrypt, C=US	2024-07-19 21:46:51	2024-10-17 21:46:50	stoff81.site, www.stoff81.site 2 entries

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
site	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=69a09e9e-9178-4617-8881-8261315e8e4d

Last Result: https://check-your-website.server-daten.de/?q=stoff81.site - 2025-01-03 13:04:37

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

<a href="https://check-your-website.server-daten.de/?q=stoff81.site" target="_blank">Check this Site: stoff81.site</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=stoff81.site