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

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
02.12.2025 11:17:04

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
wpz.pw			yes	2	2
www.wpz.pw			yes	2	2

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


	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.12.2025, 00:00:00 +, Signature-Inception: 30.11.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: pw
pw	2 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 44440, DigestType 2 and Digest NizU64yP1RZ0YiY5+GD5BuoIp8l3QAVHqfCsfbkuFMY=


	DS with Algorithm 13, KeyTag 41432, DigestType 2 and Digest qzKXUcke1mSKD3fNRaMAh3POJKTIqP1KUQw6MD4Z8aw=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner pw., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.12.2025, 05:00:00 +, Signature-Inception: 02.12.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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 50850, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner pw., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 24.12.2025, 11:14:36 +, Signature-Inception: 24.11.2025, 09:44:36 +, KeyTag 41432, Signer-Name: pw


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


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

Zone: wpz.pw
wpz.pw	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 "5catv75rqvg7booi3u66f76ek02urokk" between the hashed NSEC3-owner "5canr0t4kucpq91ov9vtge000gksrnit" and the hashed NextOwner "5cb4nfn6jjconk4stivsm4to89il6ptb". So the parent zone confirmes the not-existence of a DS RR. Bitmap: TXT, RRSIG Validated: RRSIG-Owner 5canr0t4kucpq91ov9vtge000gksrnit.pw., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.12.2025, 13:49:44 +, Signature-Inception: 24.11.2025, 12:19:44 +, KeyTag 50850, Signer-Name: pw


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "vmsqg14f37l371bnkc5kgk9tlqh9aiv0" as Owner. That's the Hash of "pw" with the NextHashedOwnerName "vmt69j4mji2037u8ajmqntukb6p0elbt". So that domain name is the Closest Encloser of "wpz.pw". Opt-Out: True. Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner vmsqg14f37l371bnkc5kgk9tlqh9aiv0.pw., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.12.2025, 11:14:36 +, Signature-Inception: 24.11.2025, 09:44:36 +, KeyTag 50850, Signer-Name: pw


	0 DNSKEY RR found




Zone: www.wpz.pw
www.wpz.pw	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
wpz.pw	T 181.ip-149-202-34.eu	149.202.34.181 Roubaix/Hauts-de-France/France (FR) - OVH SAS
	T vps-e3f05a2a.vps.ovh.net	149.202.34.181 Roubaix/Hauts-de-France/France (FR) - OVH SAS
	T	2001:41d0:52:1000::150 Roubaix/Hauts-de-France/France (FR) - OVH SAS
pw	• ns0.centralnic.net
	• ns1.nic.pw / PGXL-PS5KRW-2C7ZTP		•
	• ns2.nic.pw / CKQV-6AF162-DWW7G4		•
	• ns5.nic.pw / PGXL-PS5KRW-2C7ZTP		•
	• ns6.nic.pw / CKQV-6AF162-DWW7G4		•

4. SOA-Entries

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

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

Domain:	wpz.pw
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	3

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 "wpz.pw" is domain, public suffix is ".pw", top-level-domain is ".pw", top-level-domain-type is "country-code", Country is Palau, tld-manager is "Micronesia Investment and Development Corporation", num .pw-domains preloaded: 346 (complete: 276475)
	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 doesn't support TCP connection: 181.ip-149-202-34.eu / 149.202.34.181: Refused
X	Fatal error: Nameserver doesn't support TCP connection: vps-e3f05a2a.vps.ovh.net / 149.202.34.181: Refused
X	Fatal error: Nameserver doesn't support TCP connection: vps-e3f05a2a.vps.ovh.net / 2001:41d0:52:1000::150: Timeout
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.wpz.pw
	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: ns0.centralnic.net, ns1.nic.pw, ns2.nic.pw, ns5.nic.pw, ns6.nic.pw, 4 Name Servers included in Delegation: ns1.nic.pw, ns2.nic.pw, ns5.nic.pw, ns6.nic.pw, 4 Name Servers included in 2 Zone definitions: ns1.nic.pw, ns2.nic.pw, ns5.nic.pw, ns6.nic.pw, 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	Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
X	Nameserver Timeout checking Echo Capitalization: 181.ip-149-202-34.eu / 149.202.34.181
X	Nameserver Timeout checking Echo Capitalization: vps-e3f05a2a.vps.ovh.net / 149.202.34.181
X	Nameserver Timeout checking Echo Capitalization: vps-e3f05a2a.vps.ovh.net / 2001:41d0:52:1000::150
X	Nameserver Timeout checking EDNS512: 181.ip-149-202-34.eu / 149.202.34.181
X	Nameserver Timeout checking EDNS512: vps-e3f05a2a.vps.ovh.net / 149.202.34.181
X	Nameserver Timeout checking EDNS512: vps-e3f05a2a.vps.ovh.net / 2001:41d0:52:1000::150
	Nameserver doesn't pass all EDNS-Checks: 181.ip-149-202-34.eu / 149.202.34.181: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns0.centralnic.net: 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: ns1.nic.pw: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (PGXL-PS5KRW-2C7ZTP). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns5.nic.pw: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (PGXL-PS5KRW-2C7ZTP). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: vps-e3f05a2a.vps.ovh.net / 149.202.34.181: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: vps-e3f05a2a.vps.ovh.net / 2001:41d0:52:1000::150: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
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
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: 228824 milliseconds, 228.824 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
CN=E8, O=Let's Encrypt, C=US				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
12787002020 leaf cert	CN=E8, O=Let's Encrypt, C=US	2025-11-19 11:43:57	2026-02-17 11:43:56	*.wpz.pw, wpz.pw - 2 entries

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
wpz.pw				2	2
pw	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries	∑ Timeout
_acme-challenge.wpz.pw	gikXMau23I0XZZN2GDKQUMCKAE-mA_MlNUB9TpeU01U	looks good, correct length, correct characters	1	0
_acme-challenge.wpz.pw	tzSH9zE602YXTUCsET6JWiumRDhKCu7_rRn0LgV5lgk	looks good, correct length, correct characters	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=c029c763-4e91-4392-bb99-f5f7afb350a1

Last Result: https://check-your-website.server-daten.de/?q=wpz.pw - 2025-12-02 11:17:04

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

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