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

0 in Queue, 2 of max. 8 Checks (16:49:46)
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 |

 

X

 

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

 

Checked:
15.05.2024 18:09:31

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
px-client.net
A

yes
1
0

AAAA

yes


www.px-client.net
CNAME
ghs.googlehosted.com
yes
1
0

A
142.250.185.211
Frankfurt am Main/Hesse/Germany (DE) - Google LLC
Hostname: fra16s52-in-f19.1e100.net
yes



AAAA
2a00:1450:4001:812::2013
Frankfurt am Main/Hesse/Germany (DE) - Google LLC

yes


www.px-client.net
A
172.217.18.19
Frankfurt am Main/Hesse/Germany (DE) - Google LLC
No Hostname found
no


*.px-client.net
A
35.190.10.96
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






2 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)






1 RRSIG RR to validate DNSKEY RR found






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

net
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=






1 RRSIG RR to validate DS RR found






RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2024, 05:00:00 +, Signature-Inception: 15.05.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 37331, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 13, KeyTag 51809, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.05.2024, 14:10:35 +, Signature-Inception: 07.05.2024, 14:05:35 +, KeyTag 37331, Signer-Name: net






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






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: px-client.net

px-client.net
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 "9jsltrk688u0v7sfjtkie6722kkd43ph" between the hashed NSEC3-owner "9jsle850oa1u7uklrklm1nce9g8em0ou" and the hashed NextOwner "9jsm74u97rac3r1f6aff93mi4qiuh8gq". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 9jsle850oa1u7uklrklm1nce9g8em0ou.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2024, 06:50:15 +, Signature-Inception: 13.05.2024, 05:40:15 +, KeyTag 51809, Signer-Name: net






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "px-client.net". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2024, 06:51:45 +, Signature-Inception: 13.05.2024, 05:41:45 +, KeyTag 51809, Signer-Name: net






0 DNSKEY RR found









Zone: www.px-client.net

www.px-client.net
0 DS RR in the parent zone found



Zone: (root)

(root)
1 DS RR published






DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=






• Status: Valid because published






2 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)






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.06.2024, 00:00:00 +, Signature-Inception: 11.05.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: 28.05.2024, 05:00:00 +, Signature-Inception: 15.05.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 956, 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: 22.05.2024, 14:02:35 +, Signature-Inception: 07.05.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: googlehosted.com

googlehosted.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 "6ngrlhc9jj422bkr9n40uv7rmmq82nva" between the hashed NSEC3-owner "6ngrin33o48pqfmgrpvveo3pkg8lrpe5" and the hashed NextOwner "6ngrmfaeh5solgvl9ha91nvjhlt0e4vm". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 6ngrin33o48pqfmgrpvveo3pkg8lrpe5.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.05.2024, 06:40:56 +, Signature-Inception: 12.05.2024, 05:30:56 +, KeyTag 956, 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 "googlehosted.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: 20.05.2024, 04:25:01 +, Signature-Inception: 13.05.2024, 03:15:01 +, KeyTag 956, Signer-Name: com






0 DNSKEY RR found









Zone: ghs.googlehosted.com

ghs.googlehosted.com
0 DS RR in the parent zone found






0 DNSKEY RR found







 

3. Name Servers

DomainNameserverNS-IP
px-client.net
•  dns1.p06.nsone.net / ns1dns-fra03-910-5315-0
198.51.44.6
Toronto/Ohio/United States (US) - NSONE Inc		•

• 
2620:4d:4000:6259:7:6:0:1
Toronto/Ohio/United States (US) - NSONE Inc		•

•  dns1.p07.nsone.net / ns1dns-fra03-910-5317-0
198.51.44.7
Toronto/Ohio/United States (US) - NSONE Inc		•

• 
2620:4d:4000:6259:7:7:0:1
Toronto/Ohio/United States (US) - NSONE Inc		•

•  dns2.p06.nsone.net / ns1dns-fra03-911-5312-0
198.51.45.6
New York/United States (US) - NSONE Inc		•

• 
2a00:edc0:6259:7:6::2
Amsterdam/North Holland/The Netherlands (NL) - NS1		•

•  dns2.p07.nsone.net / ns1dns-fra03-387-5301-0
198.51.45.7
New York/United States (US) - NSONE Inc		•

• 
2a00:edc0:6259:7:7::2
Amsterdam/North Holland/The Netherlands (NL) - NS1		•

•  dns3.p06.nsone.net / ns1dns-fra03-912-5310-0
198.51.44.70
Toronto/Ohio/United States (US) - NSONE Inc		•

• 
2620:4d:4000:6259:7:6:0:3
Toronto/Ohio/United States (US) - NSONE Inc		•

•  dns3.p07.nsone.net / ns1dns-fra03-910-5308-0
198.51.44.71
Toronto/Ohio/United States (US) - NSONE Inc		•

• 
2620:4d:4000:6259:7:7:0:3
Toronto/Ohio/United States (US) - NSONE Inc		•

•  dns4.p06.nsone.net / ns1dns-fra03-387-5312-0
198.51.45.70
New York/United States (US) - NSONE Inc		•

• 
2a00:edc0:6259:7:6::4
Amsterdam/North Holland/The Netherlands (NL) - NS1		•

•  dns4.p07.nsone.net / ns1dns-fra03-341-5303-0
198.51.45.71
New York/United States (US) - NSONE Inc		•

• 
2a00:edc0:6259:7:7::4
Amsterdam/North Holland/The Netherlands (NL) - NS1		•
net
•  a.gtld-servers.net / nnn1-par6
•

•  b.gtld-servers.net / nnn1-elwaw4
•

•  c.gtld-servers.net / nnn1-defra-5
•

•  d.gtld-servers.net / nnn1-par6
•

•  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-ein2
•

•  l.gtld-servers.net / nnn1-ein1
•

•  m.gtld-servers.net / nnn1-ein4
•
ghs.googlehosted.com
•  ns1.google.com
216.239.32.10
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:32::a
Mountain View/California/United States (US) - Google LLC		•
googlehosted.com
•  ns1.google.com
216.239.32.10
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:32::a
Mountain View/California/United States (US) - Google LLC		•

•  ns2.google.com
216.239.34.10
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:34::a
Mountain View/California/United States (US) - Google LLC		•

•  ns3.google.com
216.239.36.10
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:36::a
Mountain View/California/United States (US) - Google LLC		•

•  ns4.google.com
216.239.38.10
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:38::a
Mountain View/California/United States (US) - Google LLC		•
com
•  a.gtld-servers.net / nnn1-par6
•

•  b.gtld-servers.net / nnn1-elwaw4
•

•  c.gtld-servers.net / nnn1-par6
•

•  d.gtld-servers.net / nnn1-defra-5
•

•  e.gtld-servers.net / nnn1-par6
•

•  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-ein4
•

•  k.gtld-servers.net / nnn1-nlams-2e
•

•  l.gtld-servers.net / nnn1-frmrs-2
•

•  m.gtld-servers.net / nnn1-ein4
•

 

4. SOA-Entries


Domain:net
Zone-Name:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1715789354
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:12


Domain:net
Zone-Name:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1715789364
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:1


Domain:px-client.net
Zone-Name:px-client.net
Primary:dns1.p07.nsone.net
Mail:hostmaster.nsone.net
Serial:1649591491
Refresh:21600
Retry:3600
Expire:259200
TTL:3600
num Entries:16


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1715789364
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:10


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1715789384
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:3


Domain:googlehosted.com
Zone-Name:googlehosted.com
Primary:ns1.google.com
Mail:dns-admin.google.com
Serial:633513132
Refresh:900
Retry:900
Expire:1800
TTL:60
num Entries:8


Domain:ghs.googlehosted.com
Zone-Name:googlehosted.com
Primary:ns1.google.com
Mail:dns-admin.google.com
Serial:633513132
Refresh:900
Retry:900
Expire:1800
TTL:60
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


:

:
DomainnameHttp-StatusredirectSec.G
• http://www.px-client.net/
142.250.185.211
404

Html is minified: 411.87 %
0.073
M
Not Found
Date: Wed, 15 May 2024 16:11:12 GMT
Server: ghs
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1561

• http://www.px-client.net/
172.217.18.19
404

Html is minified: 411.87 %
0.044
M
Not Found
Date: Wed, 15 May 2024 16:11:12 GMT
Server: ghs
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1561

• http://www.px-client.net/
2a00:1450:4001:812::2013
404

Html is minified: 411.87 %
0.037
M
Not Found
Date: Wed, 15 May 2024 16:11:12 GMT
Server: ghs
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1561

• https://www.px-client.net/
142.250.185.211
-16


0.037
P
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

• https://www.px-client.net/
172.217.18.19
-16


0.040
P
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

• https://www.px-client.net/
2a00:1450:4001:812::2013
-16


0.037
P
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

• http://www.px-client.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
142.250.185.211
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1142		404

Html is minified: 363.84 %
Other inline scripts (∑/total): 0/0		0.040
A
Not Found
Visible Content:
Date: Wed, 15 May 2024 16:11:13 GMT
Server: ghs
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1630

• http://www.px-client.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
172.217.18.19
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1142		404

Html is minified: 363.84 %
Other inline scripts (∑/total): 0/0		0.037
A
Not Found
Visible Content:
Date: Wed, 15 May 2024 16:11:13 GMT
Server: ghs
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1630

• http://www.px-client.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a00:1450:4001:812::2013
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1142		404

Html is minified: 363.84 %
Other inline scripts (∑/total): 0/0		0.037
A
Not Found
Visible Content:
Date: Wed, 15 May 2024 16:11:13 GMT
Server: ghs
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 1630

• https://172.217.18.19/
172.217.18.19
-16


0.040
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

• https://142.250.185.211/
142.250.185.211
-16


0.037
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

• https://[2a00:1450:4001:0812:0000:0000:0000:2013]/
2a00:1450:4001:812::2013
-16


0.037
P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

 

7. Comments


1. General Results, most used to calculate the result

Aname "px-client.net" is domain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 9305 (complete: 244198)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: www.px-client.net has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: www.px-client.net has 1 ipv4, 1 ipv6 addresses
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.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - no version with Http-Status 200
HFatal error: No https - result with http-status 200, no encryption
Mhttp://www.px-client.net/ 142.250.185.211
404

Misconfiguration - main pages should never send http status 400 - 499
Mhttp://www.px-client.net/ 172.217.18.19
404

Misconfiguration - main pages should never send http status 400 - 499
Mhttp://www.px-client.net/ 2a00:1450:4001:812::2013
404

Misconfiguration - main pages should never send http status 400 - 499
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.px-client.net, 2 ip addresses.
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 www.px-client.net, 2 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.px-client.net

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:: 25 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 8 Name Servers.
AInfo:: 25 Queries complete, 25 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.1 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 8 different Name Servers found: dns1.p06.nsone.net, dns1.p07.nsone.net, dns2.p06.nsone.net, dns2.p07.nsone.net, dns3.p06.nsone.net, dns3.p07.nsone.net, dns4.p06.nsone.net, dns4.p07.nsone.net, 4 Name Servers included in Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, 4 Name Servers included in 1 Zone definitions: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net, 1 Name Servers listed in SOA.Primary: dns1.p07.nsone.net.
AGood: Only one SOA.Primary Name Server found.: dns1.p07.nsone.net.
Error: SOA.Primary Name Server not included in the delegation set.: dns1.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns1.p06.nsone.net (198.51.44.6): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns1.p06.nsone.net (2620:4d:4000:6259:7:6:0:1): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns1.p07.nsone.net (198.51.44.7): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns1.p07.nsone.net (2620:4d:4000:6259:7:7:0:1): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns2.p06.nsone.net (198.51.45.6): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns2.p06.nsone.net (2a00:edc0:6259:7:6::2): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns2.p07.nsone.net (198.51.45.7): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns2.p07.nsone.net (2a00:edc0:6259:7:7::2): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns3.p06.nsone.net (198.51.44.70): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns3.p06.nsone.net (2620:4d:4000:6259:7:6:0:3): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns3.p07.nsone.net (198.51.44.71): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns3.p07.nsone.net (2620:4d:4000:6259:7:7:0:3): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns4.p06.nsone.net (198.51.45.70): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns4.p06.nsone.net (2a00:edc0:6259:7:6::4): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns4.p07.nsone.net (198.51.45.71): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: dns4.p07.nsone.net (2a00:edc0:6259:7:7::4): Delegation: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, Zone: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net. Name Servers defined in Delegation, missing in Zone: dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net.Name Servers defined in Zone, missing in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net.
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: 8 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 8 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 8 Name Servers, 1 Top Level Domain: net
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: nsone.net
AGood: Name servers with different Country locations found: 8 Name Servers, 2 Countries: NL, US
AInfo: Ipv4-Subnet-list: 8 Name Servers, 1 different subnets (first Byte): 198., 1 different subnets (first two Bytes): 198.51., 2 different subnets (first three Bytes): 198.51.44., 198.51.45.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 8 Name Servers with IPv6, 2 different subnets (first block): 2620:, 2a00:, 2 different subnets (first two blocks): 2620:004d:, 2a00:edc0:, 2 different subnets (first three blocks): 2620:004d:4000:, 2a00:edc0:6259:, 2 different subnets (first four blocks): 2620:004d:4000:6259:, 2a00:edc0:6259:0007:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 16 good Nameserver
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports Echo Capitalization: 16 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 16 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 16 good Nameserver
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: pki.goog is allowed to create certificates

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Some checked attribute values are enclosed in quotation marks (" or ').: 24 Html-Elements checked, 15 without problems.
IWrong: Attribute values found, not enclosed in quotation marks (" or ').: 9 Html-Elements with attributes and missing enclosed quotation marks found. 9 wrong attributes.
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: 126050 milliseconds, 126.050 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=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
7958408982
leaf cert		CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2024-08-16 00:00:00
2025-09-15 23:59:59
*.botchk.net, *.cl.botchk.net, *.cl.px-client.com, *.cl.px-client.net, *.cl.px-cloud.net, *.cl6.botchk.net, *.cl6.px-client.com, *.cl6.px-client.net, *.cl6.px-cloud.net, *.cl6-stg.botchk.net, *.cl6-stg.px-client.com, *.cl6-stg.px-client.net, *.cl6-stg.px-cloud.net, *.cl-stg.botchk.net, *.cl-stg.px-client.com, *.cl-stg.px-client.net, *.cl-stg.px-cloud.net, *.pxcdshop.com, *.px-client.com, *.px-client.net, *.px-cloud.net, *.sa.botchk.net, *.sa.px-client.com, *.sa.px-client.net, *.sa.px-cloud.net, *.sa-stg.botchk.net, *.sa-stg.px-client.com, *.sa-stg.px-client.net, *.sa-stg.px-cloud.net, botchk.net, cl.botchk.net, cl.px-client.com, cl.px-client.net, cl.px-cloud.net, cl6.botchk.net, cl6.px-client.com, cl6.px-client.net, cl6.px-cloud.net, cl6-stg.botchk.net, cl6-stg.px-client.com, cl6-stg.px-client.net, cl6-stg.px-cloud.net, cl-stg.botchk.net, cl-stg.px-client.com, cl-stg.px-client.net, cl-stg.px-cloud.net, pxcdshop.com, px-client.com, px-client.net, px-cloud.net, sa.botchk.net, sa.px-client.com, sa.px-client.net, sa.px-cloud.net, sa-stg.botchk.net, sa-stg.px-client.com, sa-stg.px-client.net, sa-stg.px-cloud.net - 58 entries


5688766744
leaf cert		CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2023-08-15 00:00:00
2024-09-13 23:59:59
*.botchk.net, *.cl.botchk.net, *.cl.px-client.com, *.cl.px-client.net, *.cl.px-cloud.net, *.cl6.botchk.net, *.cl6.px-client.com, *.cl6.px-client.net, *.cl6.px-cloud.net, *.cl6-stg.botchk.net, *.cl6-stg.px-client.com, *.cl6-stg.px-client.net, *.cl6-stg.px-cloud.net, *.cl-stg.botchk.net, *.cl-stg.px-client.com, *.cl-stg.px-client.net, *.cl-stg.px-cloud.net, *.pxcdshop.com, *.px-client.com, *.px-client.net, *.px-cloud.net, *.sa.botchk.net, *.sa.px-client.com, *.sa.px-client.net, *.sa.px-cloud.net, *.sa-stg.botchk.net, *.sa-stg.px-client.com, *.sa-stg.px-client.net, *.sa-stg.px-cloud.net, botchk.net, cl.botchk.net, cl.px-client.com, cl.px-client.net, cl.px-cloud.net, cl6.botchk.net, cl6.px-client.com, cl6.px-client.net, cl6.px-cloud.net, cl6-stg.botchk.net, cl6-stg.px-client.com, cl6-stg.px-client.net, cl6-stg.px-cloud.net, cl-stg.botchk.net, cl-stg.px-client.com, cl-stg.px-client.net, cl-stg.px-cloud.net, pxcdshop.com, px-client.com, px-client.net, px-cloud.net, sa.botchk.net, sa.px-client.com, sa.px-client.net, sa.px-cloud.net, sa-stg.botchk.net, sa-stg.px-client.com, sa-stg.px-client.net, sa-stg.px-cloud.net - 58 entries


 

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

Issuerlast 7 daysactivenum Certs
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
14167547528
leaf cert		CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2024-08-15 22:00:00
2025-09-15 21:59:59
*.botchk.net, *.cl.botchk.net, *.cl.px-client.com, *.cl.px-client.net, *.cl.px-cloud.net, *.cl6.botchk.net, *.cl6.px-client.com, *.cl6.px-client.net, *.cl6.px-cloud.net, *.cl6-stg.botchk.net, *.cl6-stg.px-client.com, *.cl6-stg.px-client.net, *.cl6-stg.px-cloud.net, *.cl-stg.botchk.net, *.cl-stg.px-client.com, *.cl-stg.px-client.net, *.cl-stg.px-cloud.net, *.pxcdshop.com, *.px-client.com, *.px-client.net, *.px-cloud.net, *.sa.botchk.net, *.sa.px-client.com, *.sa.px-client.net, *.sa.px-cloud.net, *.sa-stg.botchk.net, *.sa-stg.px-client.com, *.sa-stg.px-client.net, *.sa-stg.px-cloud.net, botchk.net, cl.botchk.net, cl.px-client.com, cl.px-client.net, cl.px-cloud.net, cl6.botchk.net, cl6.px-client.com, cl6.px-client.net, cl6.px-cloud.net, cl6-stg.botchk.net, cl6-stg.px-client.com, cl6-stg.px-client.net, cl6-stg.px-cloud.net, cl-stg.botchk.net, cl-stg.px-client.com, cl-stg.px-client.net, cl-stg.px-cloud.net, pxcdshop.com, px-client.com, px-client.net, px-cloud.net, sa.botchk.net, sa.px-client.com, sa.px-client.net, sa.px-cloud.net, sa-stg.botchk.net, sa-stg.px-client.com, sa-stg.px-client.net, sa-stg.px-cloud.net
58 entries


10149579042
leaf cert		CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2023-08-14 22:00:00
2024-09-13 21:59:59
*.botchk.net, *.cl.botchk.net, *.cl.px-client.com, *.cl.px-client.net, *.cl.px-cloud.net, *.cl6.botchk.net, *.cl6.px-client.com, *.cl6.px-client.net, *.cl6.px-cloud.net, *.cl6-stg.botchk.net, *.cl6-stg.px-client.com, *.cl6-stg.px-client.net, *.cl6-stg.px-cloud.net, *.cl-stg.botchk.net, *.cl-stg.px-client.com, *.cl-stg.px-client.net, *.cl-stg.px-cloud.net, *.pxcdshop.com, *.px-client.com, *.px-client.net, *.px-cloud.net, *.sa.botchk.net, *.sa.px-client.com, *.sa.px-client.net, *.sa.px-cloud.net, *.sa-stg.botchk.net, *.sa-stg.px-client.com, *.sa-stg.px-client.net, *.sa-stg.px-cloud.net, botchk.net, cl.botchk.net, cl.px-client.com, cl.px-client.net, cl.px-cloud.net, cl6.botchk.net, cl6.px-client.com, cl6.px-client.net, cl6.px-cloud.net, cl6-stg.botchk.net, cl6-stg.px-client.com, cl6-stg.px-client.net, cl6-stg.px-cloud.net, cl-stg.botchk.net, cl-stg.px-client.com, cl-stg.px-client.net, cl-stg.px-cloud.net, pxcdshop.com, px-client.com, px-client.net, px-cloud.net, sa.botchk.net, sa.px-client.com, sa.px-client.net, sa.px-cloud.net, sa-stg.botchk.net, sa-stg.px-client.com, sa-stg.px-client.net, sa-stg.px-cloud.net
58 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/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns1.p06.nsone.net, dns1.p07.nsone.net, dns2.p06.nsone.net, dns2.p07.nsone.net, dns3.p06.nsone.net, dns3.p07.nsone.net, dns4.p06.nsone.net, dns4.p07.nsone.net

 

QNr.DomainTypeNS used
1
net
NS
b.root-servers.net (2001:500:200::b)

Answer: 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
2
dns1.p06.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
3
dns1.p07.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
4
dns2.p06.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
5
dns2.p07.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
6
dns3.p06.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
7
dns3.p07.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
8
dns4.p06.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
9
dns4.p07.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
10
dns1.p06.nsone.net: 198.51.44.6
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
11
dns1.p06.nsone.net: 2620:4d:4000:6259:7:6:0:1
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
12
dns1.p07.nsone.net: 198.51.44.7
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
13
dns1.p07.nsone.net: 2620:4d:4000:6259:7:7:0:1
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
14
dns2.p06.nsone.net: 198.51.45.6
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
15
dns2.p06.nsone.net: 2a00:edc0:6259:7:6::2
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
16
dns2.p07.nsone.net: 198.51.45.7
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
17
dns2.p07.nsone.net: 2a00:edc0:6259:7:7::2
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
18
dns3.p06.nsone.net: 198.51.44.70
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
19
dns3.p06.nsone.net: 2620:4d:4000:6259:7:6:0:3
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
20
dns3.p07.nsone.net: 198.51.44.71
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
21
dns3.p07.nsone.net: 2620:4d:4000:6259:7:7:0:3
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
22
dns4.p06.nsone.net: 198.51.45.70
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
23
dns4.p06.nsone.net: 2a00:edc0:6259:7:6::4
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
24
dns4.p07.nsone.net: 198.51.45.71
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
25
dns4.p07.nsone.net: 2a00:edc0:6259:7:7::4
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
ghs.googlehosted.com
0

no CAA entry found
1
0
www.px-client.net



1
0
googlehosted.com
5
issue
pki.goog
1
0
px-client.net
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
px-client.net
_globalsign-domain-verification=l_BNpBAnk-rKZRyXJ9UkBfv9o6EEuuenkBrGpYNYo0
ok
1
0
px-client.net
803bb296ba0f47e8b5fbec6e01365d35
ok
1
0
px-client.net
83d000c843784d068ed87ed5a48d4dc0
ok
1
0
px-client.net
v=spf1 include:sendmail.px-client.net -all
ok
1
0
www.px-client.net


1
0
ghs.googlehosted.com

ok
1
0
_acme-challenge.px-client.net


1
0
_acme-challenge.www.px-client.net

Name Error - The domain name does not exist
1
0
_acme-challenge.ghs.googlehosted.com


1
0
_acme-challenge.px-client.net.px-client.net

 perhaps wrong
1
0
_acme-challenge.www.px-client.net.px-client.net

 perhaps wrong
1
0
_acme-challenge.www.px-client.net.www.px-client.net

Name Error - The domain name does not exist
1
0
_acme-challenge.ghs.googlehosted.com.ghs.googlehosted.com


1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

px-client.net
1
aspmx.l.google.com
05ok

A


173.194.76.27
01ok

AAAA


2a00:1450:400c:c00::1b
01ok

CNAME


00ok
MX

px-client.net
5
alt1.aspmx.l.google.com
05ok

A


142.250.153.26
01ok

AAAA


2a00:1450:4013:c16::1a
01ok

CNAME


00ok
MX

px-client.net
5
alt2.aspmx.l.google.com
05ok

A


142.251.9.27
01ok

AAAA


2a00:1450:4025:c03::1a
01ok

CNAME


00ok
MX

px-client.net
10
alt3.aspmx.l.google.com
05ok

A


142.250.150.26
01ok

AAAA


2a00:1450:4010:c1c::1b
01ok

CNAME


00ok
MX

px-client.net
10
alt4.aspmx.l.google.com
05ok

A


74.125.200.27
01ok

AAAA


2404:6800:4003:c00::1a
01ok

CNAME


00ok

				 
			

				 
			
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=71193e2b-eec9-4617-9403-7f7178e85770

				 
			


Last Result: https://check-your-website.server-daten.de/?q=px-client.net - 2024-05-15 18:09:31

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

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

				 
			

				 
			



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