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

0 in Queue, 0 of max. 8 Checks (13:05:21)
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 |

 

A

 

Top config

 

Checked:
24.09.2022 07:48:11

 

Older results

 

A - 19.09.2022 10:19:52

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
secure.publeaks.nl
A
213.108.108.222
Bennekom/Gelderland/Netherlands (NL) - Greenhost Network
No Hostname found
yes
1
0

AAAA

yes


www.secure.publeaks.nl

Name Error
yes
1
0
*.publeaks.nl
A
213.108.104.108
yes



AAAA

yes



CNAME
publeaks.nl
yes


*.secure.publeaks.nl
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
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 18733, Flags 256






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






Public Key with Algorithm 8, KeyTag 20826, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 10.10.2022, 00:00:00 +, Signature-Inception: 19.09.2022, 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 8, KeyTag 34112, DigestType 2 and Digest PFtfmzVXRVxQdRqb6evpI4yI4Z9fB/kwl2kXtRuVzSI=






1 RRSIG RR to validate DS RR found






RRSIG-Owner nl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.10.2022, 04:00:00 +, Signature-Inception: 24.09.2022, 03:00:00 +, KeyTag 20826, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 3786, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner nl., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 05.10.2022, 10:01:39 +, Signature-Inception: 21.09.2022, 04:07:35 +, KeyTag 34112, Signer-Name: nl






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






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



Zone: publeaks.nl

publeaks.nl
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 14920, DigestType 2 and Digest 5AElaOxWqHFcv5vGS9KwUU1R1GxG6TgeJN9URsNV0Io=






1 RRSIG RR to validate DS RR found






RRSIG-Owner publeaks.nl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.10.2022, 02:34:51 +, Signature-Inception: 23.09.2022, 08:07:36 +, KeyTag 3786, Signer-Name: nl






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






4 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 530, Flags 256






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






Public Key with Algorithm 8, KeyTag 10335, Flags 256






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner publeaks.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 04.10.2022, 15:43:31 +, Signature-Inception: 20.09.2022, 14:13:31 +, KeyTag 8487, Signer-Name: publeaks.nl






RRSIG-Owner publeaks.nl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 04.10.2022, 15:43:31 +, Signature-Inception: 20.09.2022, 14:13:31 +, KeyTag 14920, Signer-Name: publeaks.nl






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






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






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



Zone: secure.publeaks.nl

secure.publeaks.nl
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 213.108.108.222
Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 04.10.2022, 15:43:31 +, Signature-Inception: 20.09.2022, 14:13:31 +, KeyTag 530, Signer-Name: publeaks.nl






RRSIG Type 1 validates the A - Result: 213.108.108.222
Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 04.10.2022, 15:43:31 +, Signature-Inception: 20.09.2022, 14:13:31 +, KeyTag 530, Signer-Name: publeaks.nl






RRSIG Type 1 validates the A - Result: 213.108.108.222
Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 04.10.2022, 15:43:31 +, Signature-Inception: 20.09.2022, 14:13:31 +, KeyTag 10335, Signer-Name: publeaks.nl






RRSIG Type 1 validates the A - Result: 213.108.108.222
Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 04.10.2022, 15:43:31 +, Signature-Inception: 20.09.2022, 14:13:31 +, KeyTag 10335, Signer-Name: publeaks.nl






CNAME-Query sends a valid NSEC RR as result with the query name "secure.publeaks.nl" equal the NSEC-owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". 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, RRSIG, NSEC Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 06.10.2022, 01:25:04 +, Signature-Inception: 21.09.2022, 23:55:04 +, KeyTag 530, Signer-Name: publeaks.nl






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC RR as result with the query name "secure.publeaks.nl" equal the NSEC-owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". 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: A, RRSIG, NSEC Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 06.10.2022, 01:25:04 +, Signature-Inception: 21.09.2022, 23:55:04 +, KeyTag 530, Signer-Name: publeaks.nl






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC RR as result with the query name "secure.publeaks.nl" equal the NSEC-owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". 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, RRSIG, NSEC Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 06.10.2022, 01:25:04 +, Signature-Inception: 21.09.2022, 23:55:04 +, KeyTag 530, Signer-Name: publeaks.nl






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.secure.publeaks.nl) sends a valid NSEC RR as result with the owner name secure.publeaks.nl. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.secure.publeaks.nl) sends a valid NSEC RR as result with the query name "_443._tcp.secure.publeaks.nl" between the NSEC-owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.secure.publeaks.nl) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.secure.publeaks.nl" between the NSEC-owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 06.10.2022, 01:25:04 +, Signature-Inception: 21.09.2022, 23:55:04 +, KeyTag 530, Signer-Name: publeaks.nl






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC RR as result with the query name "secure.publeaks.nl" equal the NSEC-owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner secure.publeaks.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 06.10.2022, 01:25:04 +, Signature-Inception: 21.09.2022, 23:55:04 +, KeyTag 530, Signer-Name: publeaks.nl






Status: Good. NoData-Proof required and found.



Zone: www.secure.publeaks.nl

www.secure.publeaks.nl
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "secure.publeaks.nl" and the NextOwner "www.publeaks.nl". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC

 

3. Name Servers

DomainNameserverNS-IP
www.secure.publeaks.nl
•  ns1.greenhost.nl

secure.publeaks.nl
•  ns1.greenhost.nl / ns-gh-3.greenhost.net
213.108.104.200
Middelaar/Limburg/Netherlands (NL) - Greenhost Network		•

• 
2a00:c6c0:0:107::53
Amsterdam/North Holland/Netherlands (NL) - Greenhost BV		•
publeaks.nl
•  ns1.greenhost.nl / ns-gh-3.greenhost.net
213.108.104.200
Middelaar/Limburg/Netherlands (NL) - Greenhost Network		•

• 
2a00:c6c0:0:107::53
Amsterdam/North Holland/Netherlands (NL) - Greenhost BV		•

•  ns2.greenhost.net / ns-do-1.greenhost.net
206.81.31.94
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC		•

• 
51.210.125.146
Gravelines/Hauts-de-France/France (FR) - OVH SAS		•

• 
2001:41d0:304:100::3d1d
Gravelines/Hauts-de-France/France (FR) - OVH SAS		•

• 
2a03:b0c0:3:d0::10fc:6001
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC		•

•  ns3.greenhost.nl / ns-htz-1.greenhost.net
78.47.187.201
Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH		•

• 
2a01:4f8:c0c:2324::1
Nuremberg/Bavaria/Germany (DE) - Hetzner		•
nl
•  ns1.dns.nl / eqx-fr2-ns02-70
•

•  ns2.dns.nl / s2.bnx
•

•  ns3.dns.nl / tld-all-ber1
•

•  ns4.dns.nl / FRA1
•

 

4. SOA-Entries


Domain:nl
Zone-Name:nl
Primary:ns1.dns.nl
Mail:hostmaster.domain-registry.nl
Serial:2022092410
Refresh:3600
Retry:600
Expire:2419200
TTL:600
num Entries:4


Domain:publeaks.nl
Zone-Name:publeaks.nl
Primary:ns1.greenhost.nl
Mail:hostmaster.publeaks.nl
Serial:1578511448
Refresh:14400
Retry:7200
Expire:2419200
TTL:86400
num Entries:8


Domain:secure.publeaks.nl
Zone-Name:publeaks.nl
Primary:ns1.greenhost.nl
Mail:hostmaster.publeaks.nl
Serial:1578511448
Refresh:14400
Retry:7200
Expire:2419200
TTL:86400
num Entries:2


Domain:www.secure.publeaks.nl
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://secure.publeaks.nl/, address used: https://secure.publeaks.nl/#/, Screenshot created 2022-09-24 07:49:56 +00:0

 

Mobil (412px x 732px)

 

533 milliseconds

 

Screenshot mobile - https://secure.publeaks.nl/#/
Mobil + Landscape (732px x 412px)

 

522 milliseconds

 

Screenshot mobile landscape - https://secure.publeaks.nl/#/
Screen (1280px x 1680px)

 

956 milliseconds

 

Screenshot Desktop - https://secure.publeaks.nl/#/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport396732
content Size396897

 

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://secure.publeaks.nl/
213.108.108.222
301
https://secure.publeaks.nl/

0.113
A
Transfer-Encoding: chunked
Connection: close
Server: GlobaLeaks
Date: Sat, 24 Sep 2022 05:48:55 GMT
Content-Encoding: gzip
Content-Security-Policy: base-uri 'none';connect-src 'self';default-src 'none';font-src 'self' data:;form-action 'none';frame-ancestors 'none';img-src 'self' data:;script-src 'self' 'sha256-IYBZitj/YWbzjFFnwLPjJJmMGdSj923kzu2tdCxLKdU=';style-src 'self' 'sha256-fwyo2zCGlh85NfN4rQUlpLM7MB5cry/1AEDA/G9mQJ8=';
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-site
Permissions-Policy: camera=(),document-domain=(),fullscreen=(),geolocation=(),microphone=()
X-Frame-Options: deny
X-Content-Type-Options: nosniff
Cache-Control: no-store
Referrer-Policy: no-referrer
X-Robots-Tag: noindex
X-Check-Tor: False
Content-Language: nl
Location: https://secure.publeaks.nl/

• https://secure.publeaks.nl/
213.108.108.222
Inline-JavaScript (∑/total): 1/1319 Inline-CSS (∑/total): 1/60		200

Html is minified: 165.90 %
Other inline scripts (∑/total): 1/1319		3.040
A
Transfer-Encoding: chunked
Connection: close
Server: GlobaLeaks
Date: Sat, 24 Sep 2022 05:48:56 GMT
Content-Encoding: gzip
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Onion-Location: http://eozjdgpnnmvcfn3drxtirjcn5c27ydkzqlzn4iptam54eewhji6qlqqd.onion/
Content-Security-Policy: base-uri 'none';connect-src 'self';default-src 'none';font-src 'self' data:;form-action 'none';frame-ancestors 'none';img-src 'self' data:;script-src 'self' 'sha256-IYBZitj/YWbzjFFnwLPjJJmMGdSj923kzu2tdCxLKdU=';style-src 'self' 'sha256-fwyo2zCGlh85NfN4rQUlpLM7MB5cry/1AEDA/G9mQJ8=';
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-site
Permissions-Policy: camera=(),document-domain=(),fullscreen=(),geolocation=(),microphone=()
X-Frame-Options: deny
X-Content-Type-Options: nosniff
Cache-Control: no-store
Referrer-Policy: no-referrer
X-Robots-Tag: noindex
X-Check-Tor: False
Content-Language: nl
Content-Type: text/html

• http://secure.publeaks.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
213.108.108.222
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		0.110
A
Not Found
Visible Content: {"error_message": "Resource not found", "error_code": 6, "arguments": []}
Transfer-Encoding: chunked
Connection: close
Server: GlobaLeaks
Date: Sat, 24 Sep 2022 05:49:00 GMT
Content-Encoding: gzip
Content-Security-Policy: base-uri 'none';connect-src 'self';default-src 'none';font-src 'self' data:;form-action 'none';frame-ancestors 'none';img-src 'self' data:;script-src 'self' 'sha256-IYBZitj/YWbzjFFnwLPjJJmMGdSj923kzu2tdCxLKdU=';style-src 'self' 'sha256-fwyo2zCGlh85NfN4rQUlpLM7MB5cry/1AEDA/G9mQJ8=';
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-site
Permissions-Policy: camera=(),document-domain=(),fullscreen=(),geolocation=(),microphone=()
X-Frame-Options: deny
X-Content-Type-Options: nosniff
Cache-Control: no-store
Referrer-Policy: no-referrer
X-Robots-Tag: noindex
X-Check-Tor: False
Content-Language: nl
Content-Type: application/json

• https://213.108.108.222/
213.108.108.222
Inline-JavaScript (∑/total): 1/1319 Inline-CSS (∑/total): 1/60		200

Html is minified: 165.90 %
Other inline scripts (∑/total): 1/1319		2.877
N
Certificate error: RemoteCertificateNameMismatch
Transfer-Encoding: chunked
Connection: close
Server: GlobaLeaks
Date: Sat, 24 Sep 2022 05:49:01 GMT
Content-Encoding: gzip
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Onion-Location: http://eozjdgpnnmvcfn3drxtirjcn5c27ydkzqlzn4iptam54eewhji6qlqqd.onion/
Content-Security-Policy: base-uri 'none';connect-src 'self';default-src 'none';font-src 'self' data:;form-action 'none';frame-ancestors 'none';img-src 'self' data:;script-src 'self' 'sha256-IYBZitj/YWbzjFFnwLPjJJmMGdSj923kzu2tdCxLKdU=';style-src 'self' 'sha256-fwyo2zCGlh85NfN4rQUlpLM7MB5cry/1AEDA/G9mQJ8=';
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-site
Permissions-Policy: camera=(),document-domain=(),fullscreen=(),geolocation=(),microphone=()
X-Frame-Options: deny
X-Content-Type-Options: nosniff
Cache-Control: no-store
Referrer-Policy: no-referrer
X-Robots-Tag: noindex
X-Check-Tor: False
Content-Language: nl
Content-Type: text/html

 

7. Comments


1. General Results, most used to calculate the result

Aname "secure.publeaks.nl" is subdomain, 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: 4314 (complete: 199710)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: secure.publeaks.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: secure.publeaks.nl has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
AGood: every https has a Strict Transport Security Header
AGood: HSTS max-age is long enough, 31536000 seconds = 365 days
AGood: HSTS has includeSubdomains - directive
AGood: HSTS has preload directive
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (3 urls)
https://secure.publeaks.nl/ 213.108.108.222


Url with incomplete Content-Type - header - missing charset
http://secure.publeaks.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.108.108.222


Url with incomplete Content-Type - header - missing charset
https://213.108.108.222/ 213.108.108.222


Url with incomplete Content-Type - header - missing charset
Ahttp://secure.publeaks.nl/ 213.108.108.222
301
https://secure.publeaks.nl/
Correct redirect http - https with the same domain name
Nhttps://213.108.108.222/ 213.108.108.222
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain secure.publeaks.nl, 1 ip addresses, 1 different http results.

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


3. DNS- and NameServer - Checks

AInfo:: 4 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 4 Queries complete, 4 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.ns1.greenhost.nl (213.108.104.200, 2a00:c6c0:0:107::53), ns2.greenhost.net (2001:41d0:304:100::3d1d, 206.81.31.94, 2a03:b0c0:3:d0::10fc:6001, 51.210.125.146), ns3.greenhost.nl (2a01:4f8:c0c:2324::1, 78.47.187.201)
AGood (1 - 3.0):: An average of 1.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.greenhost.nl, ns2.greenhost.net, ns3.greenhost.nl, 3 Name Servers included in Delegation: ns1.greenhost.nl, ns2.greenhost.net, ns3.greenhost.nl, 3 Name Servers included in 1 Zone definitions: ns1.greenhost.nl, ns2.greenhost.net, ns3.greenhost.nl, 1 Name Servers listed in SOA.Primary: ns1.greenhost.nl.
AGood: Only one SOA.Primary Name Server found.: ns1.greenhost.nl.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.greenhost.nl.
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: ns1.greenhost.nl, ns2.greenhost.net, ns3.greenhost.nl
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: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 2 Top Level Domains: nl, net
AGood: Name Servers with different domain names found.: 2 different Domains found
AGood: Name servers with different Country locations found: 3 Name Servers, 3 Countries: DE, FR, NL
AInfo: Ipv4-Subnet-list: 4 Name Servers, 4 different subnets (first Byte): 206., 213., 51., 78., 4 different subnets (first two Bytes): 206.81., 213.108., 51.210., 78.47., 4 different subnets (first three Bytes): 206.81.31., 213.108.104., 51.210.125., 78.47.187.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 4 different subnets (first block): 2001:, 2a00:, 2a01:, 2a03:, 4 different subnets (first two blocks): 2001:41d0:, 2a00:c6c0:, 2a01:04f8:, 2a03:b0c0:, 4 different subnets (first three blocks): 2001:41d0:0304:, 2a00:c6c0:0000:, 2a01:04f8:0c0c:, 2a03:b0c0:0003:, 4 different subnets (first four blocks): 2001:41d0:0304:0100:, 2a00:c6c0:0000:0107:, 2a01:04f8:0c0c:2324:, 2a03:b0c0:0003:00d0:
AExcellent: Every Name Server IPv6-address starts with an unique Hex-block
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.greenhost.nl: 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.
AGood: 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

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: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://secure.publeaks.nl/ 213.108.108.222
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://213.108.108.222/ 213.108.108.222
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://secure.publeaks.nl/ 213.108.108.222
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://213.108.108.222/ 213.108.108.222
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
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: 121957 milliseconds, 121.957 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
secure.publeaks.nl
213.108.108.222
443
ok
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
secure.publeaks.nl
213.108.108.222
443
ok
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=secure.publeaks.nl


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


213.108.108.222
213.108.108.222
443
name does not match
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok

213.108.108.222
213.108.108.222
443
name does not match
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=secure.publeaks.nl


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US

 

9. Certificates

1.
1.
CN=secure.publeaks.nl
20.09.2022
19.12.2022
718 days expired		secure.publeaks.nl - 1 entry
1.
1.
CN=secure.publeaks.nl
20.09.2022

19.12.2022
718 days expired


secure.publeaks.nl - 1 entry

KeyalgorithmEC Public Key (384 bit, secp384r1)
Signatur:SHA256 With RSA-Encryption
Serial Number:03966C9A257414EB914E9D72D7E4CA5B28D4
Thumbprint:E43739658CD7417B838E47768CDACBB160EFF988
SHA256 / Certificate:O/xYeqOtzTJUVncNn5oZxOc8i4DEYfIMeVhHR0+vVOI=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):fe25686124501c4523a3df7127e209ce107c856d9362078e887ea777d292c3aa
SHA256 hex / Subject Public Key Information (SPKI):fe25686124501c4523a3df7127e209ce107c856d9362078e887ea777d292c3aa (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://r3.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 283 days

2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020

15.09.2025
expires in 283 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3832 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3832 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Small Code Update - wait one minute

 

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

Small Code Update - wait one minute

 

11. Html-Content - Entries

Summary


Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://secure.publeaks.nl/
213.108.108.222		a

3

0


0
0
0


link
other
1

0
1
0
0
0
0


meta
other
3

0


0
0
0

https://213.108.108.222/
213.108.108.222		a

3

0


0
0
0


link
other
1

0


0
0
0


meta
other
3

0


0
0
0

 

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsg∑Status
https://secure.publeaks.nl/
213.108.108.222
a

#ContentBox


1
ok















a

https://www.torproject.org/


1
ok















a

https://www.torproject.org/download/


1
ok















link
shortcut icon
data/favicon.ico
200

1
ok
application/octet-stream
X-Content-Type-Options nosniff found




6479 Bytes








meta
charset
 utf-8


1
ok















meta
description
Secure whistleblowing platform based on GlobaLeaks free and open-source software.


1
ok















meta
viewport
width=device-width, user-scalable=yes


1
ok














https://213.108.108.222/
213.108.108.222
a

#ContentBox


1
ok















a

https://www.torproject.org/


1
ok















a

https://www.torproject.org/download/


1
ok















link
shortcut icon
data/favicon.ico


1
ok















meta
charset
 utf-8


1
ok















meta
description
Secure whistleblowing platform based on GlobaLeaks free and open-source software.


1
ok















meta
viewport
width=device-width, user-scalable=yes


1
ok














 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.greenhost.nl, ns2.greenhost.net, ns3.greenhost.nl

 

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

Answer: ns1.dns.nl, ns2.dns.nl, ns3.dns.nl, ns4.dns.nl
2
ns1.greenhost.nl: 213.108.104.200, 2a00:c6c0:0:107::53
NS
ns1.dns.nl (2001:678:2c:0:194:0:28:53)

Answer: ns3.greenhost.nl
2a01:4f8:c0c:2324::1, 78.47.187.201
3
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
4
ns2.greenhost.net: 2001:41d0:304:100::3d1d, 206.81.31.94, 2a03:b0c0:3:d0::10fc:6001, 51.210.125.146
NS
a.gtld-servers.net (2001:503:a83e::2:30)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
secure.publeaks.nl
0

no CAA entry found
1
0
publeaks.nl
0

no CAA entry found
1
0
nl
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
publeaks.nl
v=spf1 include:spf.greenhost.nl ip4:213.108.108.222 ?all
ok
1
0
secure.publeaks.nl

ok
1
0
_acme-challenge.secure.publeaks.nl

Name Error - The domain name does not exist
1
0
_acme-challenge.secure.publeaks.nl.publeaks.nl
v=spf1 include:spf.greenhost.nl ip4:213.108.108.222 ?all
 perhaps wrong
1
0
_acme-challenge.secure.publeaks.nl.secure.publeaks.nl

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
secure.publeaks.nl
213.108.108.222
443
3 Ciphers34.77 sec
0 without, 3 FS
100.00 %
Complete

1
3 Ciphers
3.00 Ciphers/Check		34.77 sec34.77 sec/Check
0 without, 3 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
secure.publeaks.nl
213.108.108.222
443
ECDHE-ECDSA-CHACHA20-POLY1305
 (Recommended)
TLSv1.2
0xCC,0xA9
 FS
3 Ciphers, 34.77 sec
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
ECDSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-ECDSA-AES256-GCM-SHA384
 (Recommended)
TLSv1.2
0xC0,0x2C
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

ECDH
ECDSA
AESGCM(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
 (Recommended)
TLSv1.2
0xC0,0x2B
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=1b3ce6cd-08a5-4939-9d46-96e4e043955a

 

Last Result: https://check-your-website.server-daten.de/?q=secure.publeaks.nl - 2022-09-24 07:48:11

 

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

 

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