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

0 in Queue, 1 of max. 4 Checks (03:44:51)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

P

 

Tls-Protocol error

 

Checked:
05.08.2026 19:01:51

 

Older results

 

A - 05.08.2026 14:20:26
A - 05.08.2026 14:06:21
A - 05.08.2026 13:31:54
A - 05.08.2026 13:27:54
A - 05.08.2026 13:15:31
A - 05.08.2026 12:50:18
A - 05.08.2026 12:14:52
I - 05.08.2026 11:26:35
A - 05.08.2026 11:06:01
P - 05.08.2026 10:47:44

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
pialpha.nl
A
94.157.11.202
Amsterdam/North Holland/The Netherlands (NL) - Odido Netherlands B.V.
Hostname: 202-11-157-94.ftth.glasoperator.nl
yes
1
0

AAAA

yes


www.pialpha.nl
A

yes
1
0

AAAA

yes


*.pialpha.nl
A
94.157.11.202
yes



AAAA

yes



CNAME

yes


 

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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.08.2026, 00:00:00 +, Signature-Inception: 31.07.2026, 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: nl

nl
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 17153, DigestType 2 and Digest xd/dyR51MlYqNfPCzTCCOJS+CPIBAfGr9FyKuXOfP0k=






1 RRSIG RR to validate DS RR found






RRSIG-Owner nl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.08.2026, 05:00:00 +, Signature-Inception: 05.08.2026, 04:00:00 +, KeyTag 57780, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 467, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner nl., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 28.08.2026, 20:38:54 +, Signature-Inception: 31.07.2026, 07:37:22 +, KeyTag 17153, Signer-Name: nl






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






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



Zone: pialpha.nl

pialpha.nl
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 10154, DigestType 2 and Digest q6I3Z0Gh+DZKUxGHFYDyy/SVeWI5HNtzrtgV6cTc+nY=






1 RRSIG RR to validate DS RR found






RRSIG-Owner pialpha.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 20.08.2026, 22:56:30 +, Signature-Inception: 24.07.2026, 02:07:21 +, KeyTag 467, Signer-Name: nl






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






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 22969, Flags 256






Public Key with Algorithm 8, KeyTag 31056, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner pialpha.nl., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 10154, Signer-Name: pialpha.nl






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






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






RRSIG Type 1 validates the A - Result: 94.157.11.202
Validated: RRSIG-Owner pialpha.nl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






RRSIG Type 16 validates the TXT - Result: v=spf1 include:_spf4.pcextreme.nl include:_spf6.pcextreme.nl ~all
Validated: RRSIG-Owner pialpha.nl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






RRSIG Type 257 validates the CAA - Result: 5|iodefmailto:Martijn.Ras@GMail.com 5|issueactalis.it
Validated: RRSIG-Owner pialpha.nl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "mmgegii7egu1g9kiqpjd2h51ktobabn0" equal the hashed NSEC3-owner "mmgegii7egu1g9kiqpjd2h51ktobabn0" and the hashed NextOwner "mmgegii7egu1g9kiqpjd2h51ktobabn1". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner mmgegii7egu1g9kiqpjd2h51ktobabn0.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "mmgegii7egu1g9kiqpjd2h51ktobabn0" equal the hashed NSEC3-owner "mmgegii7egu1g9kiqpjd2h51ktobabn0" and the hashed NextOwner "mmgegii7egu1g9kiqpjd2h51ktobabn1". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner mmgegii7egu1g9kiqpjd2h51ktobabn0.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.pialpha.nl) sends a valid NSEC3 RR as result with the hashed owner name "mmgegii7egu1g9kiqpjd2h51ktobabn0" (unhashed: pialpha.nl). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner mmgegii7egu1g9kiqpjd2h51ktobabn0.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "ih9rrd037g8rff5jpiv08i926og5mf3g" (unhashed: _tcp.pialpha.nl) with the owner "ih9rrd037g8rff5jpiv08i926og5mf3f" and the NextOwner "ih9rrd037g8rff5jpiv08i926og5mf3h". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: No Bitmap? Validated: RRSIG-Owner ih9rrd037g8rff5jpiv08i926og5mf3f.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "uktvh0aovrsk0evdt2rhqbhrk9p5j68e" (unhashed: *.pialpha.nl) as the Wildcard-Expansion of the Closest Encloser of the query name "pooif7b9o6vaivfikkgb8v6b567vo0p6". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: A, RRSIG Validated: RRSIG-Owner uktvh0aovrsk0evdt2rhqbhrk9p5j68e.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.



Zone: www.pialpha.nl

www.pialpha.nl
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 "5nkg211c35rdu2kus687jbc67mtpthrg" between the hashed NSEC3-owner "5nkg211c35rdu2kus687jbc67mtpthrg" and the hashed NextOwner "5nkg211c35rdu2kus687jbc67mtpthrh". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: RRSIG, CAA Validated: RRSIG-Owner 5nkg211c35rdu2kus687jbc67mtpthrg.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






RRSIG Type 257 validates the CAA - Result: 5|iodefmailto:Martijn.Ras@GMail.com 5|issueactalis.it
Validated: RRSIG-Owner www.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






A-Query sends a valid NSEC3 RR as result with the hashed query name "5nkg211c35rdu2kus687jbc67mtpthrg" equal the hashed NSEC3-owner "5nkg211c35rdu2kus687jbc67mtpthrg" and the hashed NextOwner "5nkg211c35rdu2kus687jbc67mtpthrh". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner 5nkg211c35rdu2kus687jbc67mtpthrg.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "5nkg211c35rdu2kus687jbc67mtpthrg" equal the hashed NSEC3-owner "5nkg211c35rdu2kus687jbc67mtpthrg" and the hashed NextOwner "5nkg211c35rdu2kus687jbc67mtpthrh". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner 5nkg211c35rdu2kus687jbc67mtpthrg.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "5nkg211c35rdu2kus687jbc67mtpthrg" equal the hashed NSEC3-owner "5nkg211c35rdu2kus687jbc67mtpthrg" and the hashed NextOwner "5nkg211c35rdu2kus687jbc67mtpthrh". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner 5nkg211c35rdu2kus687jbc67mtpthrg.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "5nkg211c35rdu2kus687jbc67mtpthrg" equal the hashed NSEC3-owner "5nkg211c35rdu2kus687jbc67mtpthrg" and the hashed NextOwner "5nkg211c35rdu2kus687jbc67mtpthrh". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner 5nkg211c35rdu2kus687jbc67mtpthrg.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.www.pialpha.nl) sends a valid NSEC3 RR as result with the hashed owner name "5nkg211c35rdu2kus687jbc67mtpthrg" (unhashed: www.pialpha.nl). So that's the Closest Encloser of the query name.
Bitmap: RRSIG, CAA Validated: RRSIG-Owner 5nkg211c35rdu2kus687jbc67mtpthrg.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "190vavsm723k3qmm5o9pciug3ggpbci8" (unhashed: _tcp.www.pialpha.nl) with the owner "190vavsm723k3qmm5o9pciug3ggpbci7" and the NextOwner "190vavsm723k3qmm5o9pciug3ggpbci9". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: No Bitmap? Validated: RRSIG-Owner 190vavsm723k3qmm5o9pciug3ggpbci7.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "v2f70fp7gnoqkmi47agjil4d2ef7gup1" (unhashed: *.www.pialpha.nl) with the owner "v2f70fp7gnoqkmi47agjil4d2ef7gup0" and the NextOwner "v2f70fp7gnoqkmi47agjil4d2ef7gup2". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: No Bitmap? Validated: RRSIG-Owner v2f70fp7gnoqkmi47agjil4d2ef7gup0.pialpha.nl., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 13.08.2026, 00:00:00 +, Signature-Inception: 23.07.2026, 00:00:00 +, KeyTag 31056, Signer-Name: pialpha.nl






Status: Good. NXDomain-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
www.pialpha.nl
•  ns051.auroradns.eu / ns051.auroradns.eu
•
pialpha.nl
•  ns051.auroradns.eu / ns051.auroradns.eu
185.95.31.118
Amsterdam/North Holland/The Netherlands (NL) - PCEXTREME		•

• 
2a00:f10:402:781:1c00:d0ff:fe00:2521
Flushing/Zeeland/The Netherlands (NL) - PCextreme		•

•  ns052.auroradns.nl / ns052.auroradns.nl
31.25.98.35
Amsterdam/North Holland/The Netherlands (NL) - Your Hosting B.V		•

• 
2a05:1500:702:0:1c00:a2ff:fe00:1f
Flushing/Zeeland/The Netherlands (NL) - PCextreme B.V. - Haarlem		•

•  ns053.auroradns.info / ns053.auroradns.info
195.8.208.24
Drachten/Friesland/The Netherlands (NL) - BIT BV		•

• 
2a05:1500:fe00::c3ff:fe08:d018
Flushing/Zeeland/The Netherlands (NL) - BIT BV		•
nl
•  ns1.dns.nl / i3d-de3-ns01-150030
•

•  ns3.dns.nl / tld-all-ffm1@53024
•

•  ns4.dns.nl / FRA2
•

 

4. SOA-Entries


Domain:nl
Zone-Name:nl
Primary:ns1.dns.nl
Mail:dns.sidn.nl
Serial:2026080533
Refresh:3600
Retry:600
Expire:1209600
TTL:600
num Entries:3


Domain:pialpha.nl
Zone-Name:pialpha.nl
Primary:ns051.auroradns.eu
Mail:admin.auroradns.eu
Serial:2019011601
Refresh:86400
Retry:7200
Expire:604800
TTL:300
num Entries:6


Domain:www.pialpha.nl
Zone-Name:pialpha.nl
Primary:ns051.auroradns.eu
Mail:admin.auroradns.eu
Serial:2019011601
Refresh:86400
Retry:7200
Expire:604800
TTL:300
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


:

:
DomainnameHttp-StatusredirectSec.G
• http://pialpha.nl/
94.157.11.202
301
https://pialpha.nl/
Html is minified: 102.69 %
0.070
A
Date: Wed, 05 Aug 2026 17:02:29 GMT
Server: Apache
Cache-Control: no-store, must-revalidate, no-cache, max-age=86400
Pragma: no-cache
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
Permissions-Policy: camera=(), microphone=(), geolocation=()
Referrer-Policy: no-referrer
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
Location: https://pialpha.nl/
Expires: 0
Content-Length: 267
Content-Type: text/html; charset=iso-8859-1

• https://pialpha.nl/
94.157.11.202
-103


0.080
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• http://pialpha.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
94.157.11.202
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://pialpha.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 102.13 %
Other inline scripts (∑/total): 0/0		0.040
A
Visible Content:
Date: Wed, 05 Aug 2026 17:02:29 GMT
Server: Apache
Cache-Control: no-store, must-revalidate, no-cache, max-age=86400
Pragma: no-cache
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
Permissions-Policy: camera=(), microphone=(), geolocation=()
Referrer-Policy: no-referrer
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
Location: https://pialpha.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Expires: 0
Content-Length: 336
Content-Type: text/html; charset=iso-8859-1

• https://pialpha.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-103


0.083
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.
Visible Content:

• https://94.157.11.202/
94.157.11.202
-103


0.080
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

 

7. Comments


1. General Results, most used to calculate the result

Aname "pialpha.nl" is domain, public suffix is ".nl", top-level-domain is ".nl", top-level-domain-type is "country-code", Country is Netherlands (the), tld-manager is "SIDN (Stichting Internet Domeinregistratie Nederland)", num .nl-domains preloaded: 6052 (complete: 276475)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: pialpha.nl has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: pialpha.nl has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
CError - no version with Http-Status 200
HFatal error: No https - result with http-status 200, no encryption
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain pialpha.nl, 1 ip addresses.
BNo _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.pialpha.nl

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 22 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 22 Queries complete, 22 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns052.auroradns.nl (2a05:1500:702:0:1c00:a2ff:fe00:1f, 31.25.98.35)
Ok (4 - 8):: An average of 7.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns051.auroradns.eu, ns052.auroradns.nl, ns053.auroradns.info, 3 Name Servers included in Delegation: ns051.auroradns.eu, ns052.auroradns.nl, ns053.auroradns.info, 3 Name Servers included in 1 Zone definitions: ns051.auroradns.eu, ns052.auroradns.nl, ns053.auroradns.info, 1 Name Servers listed in SOA.Primary: ns051.auroradns.eu.
AGood: Only one SOA.Primary Name Server found.: ns051.auroradns.eu.
AGood: SOA.Primary Name Server included in the delegation set.: ns051.auroradns.eu.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns051.auroradns.eu, ns052.auroradns.nl, ns053.auroradns.info
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 3 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 3 Top Level Domains: eu, nl, info
AGood: Name Servers with different domain names found.: 3 different Domains found
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: NL
AInfo: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 185., 195., 31., 3 different subnets (first two Bytes): 185.95., 195.8., 31.25., 3 different subnets (first three Bytes): 185.95.31., 195.8.208., 31.25.98.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2a00:, 2a05:, 2 different subnets (first two blocks): 2a00:0f10:, 2a05:1500:, 3 different subnets (first three blocks): 2a00:0f10:0402:, 2a05:1500:0702:, 2a05:1500:fe00:, 3 different subnets (first four blocks): 2a00:0f10:0402:0781:, 2a05:1500:0702:0000:, 2a05:1500:fe00:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: actalis.it is allowed to create certificates

4. Content- and Performance-critical Checks

https://pialpha.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-103

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 52980 milliseconds, 52.980 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)

Issuerlast 7 daysactivenum Certs
CN=Actalis Domain Validated TLS Server ECC CA 2025, O=Actalis S.p.A., L=Ponte San Pietro, C=IT, ST=Bergamo
0
2
2
CN=YE1, O=Let's Encrypt, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
16234317995
leaf cert		CN=Actalis Domain Validated TLS Server ECC CA 2025, O=Actalis S.p.A., L=Ponte San Pietro, C=IT, ST=Bergamo
2026-08-02 12:01:38
2026-11-02 13:00:38
pialpha.nl, www.pialpha.nl - 2 entries


16234287868
precert		CN=Actalis Domain Validated TLS Server ECC CA 2025, O=Actalis S.p.A., L=Ponte San Pietro, C=IT, ST=Bergamo
2026-08-02 11:58:49
2026-11-02 12:57:49
pialpha.nl, www.pialpha.nl - 2 entries


16220965180
leaf cert		CN=YE1, O=Let's Encrypt, C=US
2026-08-01 17:51:15
2026-10-30 17:51:14
*.pialpha.nl, pialpha.nl - 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: ns051.auroradns.eu, ns052.auroradns.nl, ns053.auroradns.info

 

QNr.DomainTypeNS used
1
eu
NS
k.root-servers.net (2001:7fd::1)

Answer: be.dns.eu, si.dns.eu, w.dns.eu, x.dns.eu, y.dns.eu
2
ns051.auroradns.eu
NS
si.dns.eu (2001:1470:8000:100::62)

Answer: ns041.auroradns.eu, ns042.auroradns.nl, ns043.auroradns.info

Answer: ns041.auroradns.eu
185.95.31.236, 2a00:f10:402:781:1c00:89ff:fe00:2597
3
nl
NS
f.root-servers.net (2001:500:2f::f)

Answer: ns1.dns.nl, ns3.dns.nl, ns4.dns.nl
4
ns052.auroradns.nl: 2a05:1500:702:0:1c00:a2ff:fe00:1f, 31.25.98.35
NS
ns1.dns.nl (2001:678:2c:0:194:0:28:53)
5
info
NS
f.root-servers.net (2001:500:2f::f)

Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
6
ns053.auroradns.info
NS
a0.info.afilias-nst.info (2001:500:19::1)

Answer: ns111.auroradns.eu, ns112.auroradns.nl, ns113.auroradns.info

Answer: ns113.auroradns.info
195.8.208.30, 2a05:1500:fe00::c3ff:fe08:d01e
7
ns042.auroradns.nl
NS
ns1.dns.nl (2001:678:2c:0:194:0:28:53)

Answer: ns051.auroradns.eu, ns052.auroradns.nl, ns053.auroradns.info

Answer: ns052.auroradns.nl
2a05:1500:702:0:1c00:a2ff:fe00:1f, 31.25.98.35
8
ns043.auroradns.info
NS
a0.info.afilias-nst.info (2001:500:19::1)

Answer: ns111.auroradns.eu, ns112.auroradns.nl, ns113.auroradns.info

Answer: ns113.auroradns.info
195.8.208.30, 2a05:1500:fe00::c3ff:fe08:d01e
9
ns111.auroradns.eu
NS
si.dns.eu (2001:1470:8000:100::62)

Answer: ns041.auroradns.eu, ns042.auroradns.nl, ns043.auroradns.info

Answer: ns041.auroradns.eu
185.95.31.236, 2a00:f10:402:781:1c00:89ff:fe00:2597
10
ns112.auroradns.nl
NS
ns1.dns.nl (2001:678:2c:0:194:0:28:53)

Answer: ns051.auroradns.eu, ns052.auroradns.nl, ns053.auroradns.info

Answer: ns052.auroradns.nl
2a05:1500:702:0:1c00:a2ff:fe00:1f, 31.25.98.35
11
ns042.auroradns.nl: 31.25.98.34
A
ns052.auroradns.nl (2a05:1500:702:0:1c00:a2ff:fe00:1f)
12
ns042.auroradns.nl: 2a05:1500:702:0:1c00:8fff:fe00:1e
AAAA
ns052.auroradns.nl (2a05:1500:702:0:1c00:a2ff:fe00:1f)
13
ns043.auroradns.info: 195.8.208.23
A
ns113.auroradns.info (2a05:1500:fe00::c3ff:fe08:d01e)
14
ns043.auroradns.info: 2a05:1500:fe00::c3ff:fe08:d017
AAAA
ns113.auroradns.info (2a05:1500:fe00::c3ff:fe08:d01e)
15
ns111.auroradns.eu: 185.95.31.184
A
ns041.auroradns.eu (2a00:f10:402:781:1c00:89ff:fe00:2597)
16
ns111.auroradns.eu: 2a00:f10:402:781:1c00:a1ff:fe00:2563
AAAA
ns041.auroradns.eu (2a00:f10:402:781:1c00:89ff:fe00:2597)
17
ns112.auroradns.nl: 31.25.98.54
A
ns052.auroradns.nl (2a05:1500:702:0:1c00:a2ff:fe00:1f)
18
ns112.auroradns.nl: 2a05:1500:702:0:1c00:20ff:fe00:32
AAAA
ns052.auroradns.nl (2a05:1500:702:0:1c00:a2ff:fe00:1f)
19
ns051.auroradns.eu: 185.95.31.118
A
ns041.auroradns.eu (2a00:f10:402:781:1c00:89ff:fe00:2597)
20
ns051.auroradns.eu: 2a00:f10:402:781:1c00:d0ff:fe00:2521
AAAA
ns041.auroradns.eu (2a00:f10:402:781:1c00:89ff:fe00:2597)
21
ns053.auroradns.info: 195.8.208.24
A
ns111.auroradns.eu (2a00:f10:402:781:1c00:a1ff:fe00:2563)
22
ns053.auroradns.info: 2a05:1500:fe00::c3ff:fe08:d018
AAAA
ns111.auroradns.eu (2a00:f10:402:781:1c00:a1ff:fe00:2563)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.pialpha.nl
5
issue
actalis.it
1
0

5
iodef
mailto:Martijn.Ras@GMail.com
1
0
pialpha.nl
5
issue
actalis.it
1
0

5
iodef
mailto:Martijn.Ras@GMail.com
1
0
nl
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
pialpha.nl
v=spf1 include:_spf4.pcextreme.nl include:_spf6.pcextreme.nl ~all
ok
1
0
www.pialpha.nl

ok
1
0
_acme-challenge.pialpha.nl

missing entry or wrong length
1
0
_acme-challenge.www.pialpha.nl

Name Error - The domain name does not exist
1
0
_acme-challenge.pialpha.nl.pialpha.nl

 perhaps wrong
1
0
_acme-challenge.www.pialpha.nl.pialpha.nl

 perhaps wrong
1
0
_acme-challenge.www.pialpha.nl.www.pialpha.nl

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

pialpha.nl
10
primary.mail.pcextreme.nl
02ok

A


185.66.250.200
05ok

A


185.66.250.201
05ok

A


185.87.185.193
05ok

A


185.107.224.99
05ok

A


185.87.186.222
05ok

AAAA


2a00:f10:121:a00:4f8:84ff:fe00:1846
05ok

AAAA


2a00:f10:121:a00:470:4ff:fe00:1845
05ok

AAAA


2a00:f10:400:2:488:56ff:fe00:74f
05ok

AAAA


2a00:f10:400:2:44a:acff:fe00:33f
05ok

AAAA


2a00:f10:121:b00:43f:e2ff:fe00:1cfb
05ok

CNAME


00ok
MX

pialpha.nl
20
fallback.mail.pcextreme.nl
02ok

A


185.87.185.193
05ok

A


185.87.186.222
05ok

A


185.66.250.200
05ok

A


185.107.224.99
05ok

A


185.66.250.201
05ok

AAAA


2a00:f10:121:a00:470:4ff:fe00:1845
05ok

AAAA


2a00:f10:121:a00:4f8:84ff:fe00:1846
05ok

AAAA


2a00:f10:400:2:488:56ff:fe00:74f
05ok

AAAA


2a00:f10:400:2:44a:acff:fe00:33f
05ok

AAAA


2a00:f10:121:b00:43f:e2ff:fe00:1cfb
05ok

CNAME


00ok
SPF
TXT
pialpha.nl

v=spf1 include:_spf4.pcextreme.nl include:_spf6.pcextreme.nl ~all
ok

TXT
_spf4.pcextreme.nl

v=spf1 a:spf.route25.eu ip4:109.72.85.0/24 ip4:109.72.86.0/24 ip4:109.72.87.128/25 ip4:185.103.240.22/32 ~all
ok

TXT
_spf6.pcextreme.nl

v=spf1 ip6:2a00:f10:101::/48 ip6:2a00:f10:10a:e::/64 ip6:2a00:1d20:3:2::25:587:41/48 ip6:2a05:1500:300:2::/64 ip6:2a05:1500:600:13::/64 ~all
ok

A
spf.route25.eu

185.107.213.237
ok

A
spf.route25.eu

185.95.31.77
ok

A
spf.route25.eu

185.95.31.95
ok

A
spf.route25.eu

185.95.31.121
ok

A
spf.route25.eu

185.87.187.41
ok

A
spf.route25.eu

185.95.31.168
ok

A
spf.route25.eu

185.87.185.193
ok

A
spf.route25.eu

185.87.184.60
ok

A
spf.route25.eu

185.66.250.201
ok

A
spf.route25.eu

185.66.250.200
ok

A
spf.route25.eu

185.107.224.99
ok

A
spf.route25.eu

185.95.31.172
ok

A
spf.route25.eu

185.66.250.215
ok

A
spf.route25.eu

185.107.213.52
ok

A
spf.route25.eu

185.103.243.60
ok

A
spf.route25.eu

185.87.186.222
ok

A
spf.route25.eu

185.103.159.25
ok

A
spf.route25.eu

185.107.227.77
ok

AAAA
spf.route25.eu

2a00:f10:121:a00:1c00:efff:fe00:1854
ok

AAAA
spf.route25.eu

2a00:f10:121:a00:470:4ff:fe00:1845
ok

AAAA
spf.route25.eu

2a00:f10:121:a00:4f8:84ff:fe00:1846
ok

AAAA
spf.route25.eu

2a00:f10:121:b00:1c00:25ff:fe00:1b5b
ok

AAAA
spf.route25.eu

2a00:f10:121:b00:1c00:bcff:fe00:1c14
ok

AAAA
spf.route25.eu

2a00:f10:121:b00:43f:e2ff:fe00:1cfb
ok

AAAA
spf.route25.eu

2a00:f10:305:0:1c00:d8ff:fe00:461
ok

AAAA
spf.route25.eu

2a00:f10:400:2:44a:acff:fe00:33f
ok

AAAA
spf.route25.eu

2a00:f10:400:2:488:56ff:fe00:74f
ok

AAAA
spf.route25.eu

2a00:f10:400:2:4df:4aff:fe00:1c4
ok

AAAA
spf.route25.eu

2a00:f10:400:4:1c00:18ff:fe00:1617
ok

AAAA
spf.route25.eu

2a00:f10:401:0:1c00:a4ff:fe00:fb
ok

AAAA
spf.route25.eu

2a00:f10:402:781:1c00:26ff:fe00:2553
ok

AAAA
spf.route25.eu

2a00:f10:402:781:1c00:42ff:fe00:2557
ok

AAAA
spf.route25.eu

2a00:f10:402:781:1c00:45ff:fe00:24f8
ok

AAAA
spf.route25.eu

2a00:f10:402:781:1c00:56ff:fe00:2524
ok

AAAA
spf.route25.eu

2a00:f10:402:781:1c00:b9ff:fe00:250a
ok

AAAA
spf.route25.eu

2a05:1500:300:2:4c1:10ff:fe00:1ce
ok

				 
			

				 
			
17. Cipher Suites
No results 

				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=b4cecd24-0dbd-4a06-8cbb-2367c51655c3

				 
			


Last Result: https://check-your-website.server-daten.de/?q=pialpha.nl - 2026-08-05 19:01:51

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

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

				 
			

				 
			



Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • 
USt-IdNr.: DE221734518

				 
			


Errors, ideas, questions? Use the 
Contact form • A project using

Server-Daten - Web Database solutions