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

0 in Queue, 0 of max. 8 Checks (17:17:33)
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:
02.03.2021 16:45:23

 

Older results

 

A - 02.03.2021 15:46:30

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
chat.bakkerspees.nl
CNAME
proxy.bakkerspees.nl
yes
1
0

A
185.218.72.33
Amsterdam/North Holland/Netherlands (NL) - Bakker & Spees BV
No Hostname found
yes


www.chat.bakkerspees.nl

Name Error
yes
1
0
*.bakkerspees.nl
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.chat.bakkerspees.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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 42351, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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






2 RRSIG RR to validate DS RR found






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






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 4309, 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: 09.03.2021, 08:55:28 +, Signature-Inception: 23.02.2021, 01:08:12 +, 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: bakkerspees.nl

bakkerspees.nl
1 DS RR in the parent zone found






DS with Algorithm 7, KeyTag 36711, DigestType 2 and Digest nmhWkGFVC9N1ZqCKtRFY9IHg+9EDJl5ne6medrjei5k=






2 RRSIG RR to validate DS RR found






RRSIG-Owner bakkerspees.nl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 15.03.2021, 17:33:40 +, Signature-Inception: 01.03.2021, 04:40:50 +, KeyTag 4309, Signer-Name: nl






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






3 DNSKEY RR found






Public Key with Algorithm 7, KeyTag 5873, Flags 256






Public Key with Algorithm 7, KeyTag 13862, Flags 256






Public Key with Algorithm 7, KeyTag 36711, Flags 257 (SEP = Secure Entry Point)






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner bakkerspees.nl., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






RRSIG-Owner bakkerspees.nl., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 36711, Signer-Name: bakkerspees.nl






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 13862 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 36711 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 36711, DigestType 2 and Digest "nmhWkGFVC9N1ZqCKtRFY9IHg+9EDJl5ne6medrjei5k=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: chat.bakkerspees.nl

chat.bakkerspees.nl
0 DS RR in the parent zone found






RRSIG Type 5 validates the CNAME - Result: proxy.bakkerspees.nl
Validated: RRSIG-Owner chat.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 3600 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl



Zone: www.chat.bakkerspees.nl

www.chat.bakkerspees.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 "hovcbg1u3f7auk43thfnmcv6gugfl2kj" between the hashed NSEC3-owner "ha9ukgfvc4k9j3q1un2er8c84gfceril" and the hashed NextOwner "i0knukroos9hk863grmtgv1s33p4s8o2". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner ha9ukgfvc4k9j3q1un2er8c84gfceril.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "2e7etre1mmauv17epr88togvgldkdrp6" as Owner. That's the Hash of "chat.bakkerspees.nl" with the NextHashedOwnerName "2hccaul6rd89o4dppbikc8dou5r02kq3". So that domain name is the Closest Encloser of "www.chat.bakkerspees.nl". Opt-Out: False.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 2e7etre1mmauv17epr88togvgldkdrp6.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






The ClosestEncloser says, that "*.chat.bakkerspees.nl" with the Hash "s99aolvhk1tpnoghab7h3tu3dsh0mloq" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "s5uc42g4n0h2icjsh6nr34m9qv67p1v2" and the Next Owner "sj03d1fuqmtovkt87679r32ule4nc63v", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner s5uc42g4n0h2icjsh6nr34m9qv67p1v2.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl



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 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 42351, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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






2 RRSIG RR to validate DS RR found






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






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 4309, 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: 09.03.2021, 08:55:28 +, Signature-Inception: 23.02.2021, 01:08:12 +, 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: bakkerspees.nl

bakkerspees.nl
1 DS RR in the parent zone found






DS with Algorithm 7, KeyTag 36711, DigestType 2 and Digest nmhWkGFVC9N1ZqCKtRFY9IHg+9EDJl5ne6medrjei5k=






2 RRSIG RR to validate DS RR found






RRSIG-Owner bakkerspees.nl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 15.03.2021, 17:33:40 +, Signature-Inception: 01.03.2021, 04:40:50 +, KeyTag 4309, Signer-Name: nl






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






3 DNSKEY RR found






Public Key with Algorithm 7, KeyTag 5873, Flags 256






Public Key with Algorithm 7, KeyTag 13862, Flags 256






Public Key with Algorithm 7, KeyTag 36711, Flags 257 (SEP = Secure Entry Point)






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner bakkerspees.nl., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






RRSIG-Owner bakkerspees.nl., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 36711, Signer-Name: bakkerspees.nl






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 13862 used to validate the DNSKEY RRSet






• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 36711 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 36711, DigestType 2 and Digest "nmhWkGFVC9N1ZqCKtRFY9IHg+9EDJl5ne6medrjei5k=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: proxy.bakkerspees.nl

proxy.bakkerspees.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 "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" between the hashed NSEC3-owner "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" and the hashed NextOwner "2218fougbgkkb85cbb4os2vib5i6aujg". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1t7q4423ic8tev5fpsqf1b4a1iff8vgn.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 185.218.72.33
Validated: RRSIG-Owner proxy.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 3600 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" equal the hashed NSEC3-owner "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" and the hashed NextOwner "2218fougbgkkb85cbb4os2vib5i6aujg". 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 Validated: RRSIG-Owner 1t7q4423ic8tev5fpsqf1b4a1iff8vgn.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" equal the hashed NSEC3-owner "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" and the hashed NextOwner "2218fougbgkkb85cbb4os2vib5i6aujg". 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 Validated: RRSIG-Owner 1t7q4423ic8tev5fpsqf1b4a1iff8vgn.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" equal the hashed NSEC3-owner "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" and the hashed NextOwner "2218fougbgkkb85cbb4os2vib5i6aujg". 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 Validated: RRSIG-Owner 1t7q4423ic8tev5fpsqf1b4a1iff8vgn.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.proxy.bakkerspees.nl) sends a valid NSEC3 RR as result with the hashed owner name "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" (unhashed: proxy.bakkerspees.nl). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1t7q4423ic8tev5fpsqf1b4a1iff8vgn.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "ul1tuf5dpm57r1kietrs697g8dgun7oa" (unhashed: _tcp.proxy.bakkerspees.nl) with the owner "uk63mg3irk2ts5f1fn2bge9s0fi85etu" and the NextOwner "ulhns53ctu75kt9kdgcvio0l4c8gesjf". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG, CAA Validated: RRSIG-Owner uk63mg3irk2ts5f1fn2bge9s0fi85etu.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.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 "vjfm51ksrnprun5tlgs85q1lurc589ps" (unhashed: *.proxy.bakkerspees.nl) with the owner "vbfja28fqhe0pujav4q462aco1uebmp1" and the NextOwner "vn11c11dgf4g0lolv58afc3tqv410e04". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner vbfja28fqhe0pujav4q462aco1uebmp1.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 09:09:39 +, Signature-Inception: 02.03.2021, 09:09:39 +, KeyTag 13862, Signer-Name: bakkerspees.nl






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" equal the hashed NSEC3-owner "1t7q4423ic8tev5fpsqf1b4a1iff8vgn" and the hashed NextOwner "2218fougbgkkb85cbb4os2vib5i6aujg". 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 Validated: RRSIG-Owner 1t7q4423ic8tev5fpsqf1b4a1iff8vgn.bakkerspees.nl., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 11.03.2021, 00:00:00 +, Signature-Inception: 18.02.2021, 00:00:00 +, KeyTag 13862, Signer-Name: bakkerspees.nl






Status: Good. NoData-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
www.chat.bakkerspees.nl
•  ns0.transip.net

bakkerspees.nl
•  ns0.transip.net
195.135.195.195
Rome/Latium/Italy (IT) - Transip B.V.		•

• 
2a01:7c8:dddd:195::195
Rotterdam/South Holland/Netherlands (NL) - Transip B.V.		•

•  ns1.transip.nl
195.8.195.195
Leiden/South Holland/Netherlands (NL) - Transip B.V.		•

• 
2a01:7c8:7000:195::195
Leiden/South Holland/Netherlands (NL) - Transip B.V.		•

•  ns2.transip.eu / auth1
37.97.199.195
Zaandam/North Holland/Netherlands (NL) - Transip B.V.		•

• 
2a01:7c8:f:c1f::195
Leiden/South Holland/Netherlands (NL) - TransIP B.V. Amsterdam network		•
nl
•  ns1.dns.nl / LHR2
•

•  ns2.dns.nl / s2.amx
•

•  ns3.dns.nl / tld-all-ber1
•
proxy.bakkerspees.nl
•  ns0.transip.net
195.135.195.195
Rome/Latium/Italy (IT) - Transip B.V.		•

• 
2a01:7c8:dddd:195::195
Rotterdam/South Holland/Netherlands (NL) - Transip B.V.		•
bakkerspees.nl
•  ns0.transip.net / auth1
195.135.195.195
Rome/Latium/Italy (IT) - Transip B.V.		•

• 
2a01:7c8:dddd:195::195
Rotterdam/South Holland/Netherlands (NL) - Transip B.V.		•

•  ns1.transip.nl
195.8.195.195
Leiden/South Holland/Netherlands (NL) - Transip B.V.		•

• 
2a01:7c8:7000:195::195
Leiden/South Holland/Netherlands (NL) - Transip B.V.		•

•  ns2.transip.eu / auth1
37.97.199.195
Zaandam/North Holland/Netherlands (NL) - Transip B.V.		•

• 
2a01:7c8:f:c1f::195
Leiden/South Holland/Netherlands (NL) - TransIP B.V. Amsterdam network		•
nl
•  ns1.dns.nl / LHR2
•

•  ns2.dns.nl / s2.amx
•

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

 

4. SOA-Entries


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


Domain:bakkerspees.nl
Zone-Name:bakkerspees.nl
Primary:ns0.transip.net
Mail:hostmaster.transip.nl
Serial:2021030203
Refresh:86400
Retry:1800
Expire:2419200
TTL:300
num Entries:6


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


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


Domain:bakkerspees.nl
Zone-Name:bakkerspees.nl
Primary:ns0.transip.net
Mail:hostmaster.transip.nl
Serial:2021030203
Refresh:86400
Retry:1800
Expire:2419200
TTL:300
num Entries:6


Domain:proxy.bakkerspees.nl
Zone-Name:bakkerspees.nl
Primary:ns0.transip.net
Mail:hostmaster.transip.nl
Serial:2021030203
Refresh:86400
Retry:1800
Expire:2419200
TTL:300
num Entries:2


5. Screenshots

Startaddress: https://chat.bakkerspees.nl, address used: https://chat.bakkerspees.nl/home, Screenshot created 2021-03-02 16:46:50 +00:0

 

Mobil (412px x 732px)

 

1008 milliseconds

 

Screenshot mobile - https://chat.bakkerspees.nl/home
Mobil + Landscape (732px x 412px)

 

1072 milliseconds

 

Screenshot mobile landscape - https://chat.bakkerspees.nl/home
Screen (1280px x 1680px)

 

1239 milliseconds

 

Screenshot Desktop - https://chat.bakkerspees.nl/home

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

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

 

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_256_GCM.

 

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://chat.bakkerspees.nl/
185.218.72.33
301
https://chat.bakkerspees.nl/
Html is minified: 108.54 %
0.040
A
Server: nginx
Date: Tue, 02 Mar 2021 15:46:10 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://chat.bakkerspees.nl/
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block

• https://chat.bakkerspees.nl/
185.218.72.33
Inline-JavaScript (∑/total): 3/1265 Inline-CSS (∑/total): 1/966		200

Html is minified: 101.37 %
Other inline scripts (∑/total): 2/1265		2.350
A
small visible content (num chars: 0)
Server: nginx
Date: Tue, 02 Mar 2021 15:46:10 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
X-XSS-Protection: 1,1; mode=block
X-Content-Type-Options: nosniff,nosniff
X-Instance-ID: 2SqoGnEiPYDM75fHH
Vary: Accept-Encoding
Content-Encoding: gzip
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Frame-Options: SAMEORIGIN

• http://chat.bakkerspees.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
185.218.72.33
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://chat.bakkerspees.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 108.54 %
Other inline scripts (∑/total): 0/0		0.037
A
Visible Content: 301 Moved Permanently nginx
Server: nginx
Date: Tue, 02 Mar 2021 15:46:14 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://chat.bakkerspees.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block

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

Inline-JavaScript (∑/total): 3/1265 Inline-CSS (∑/total): 1/966		200

Html is minified: 101.37 %
Other inline scripts (∑/total): 2/1265		2.317

Visible Content:
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
Server: nginx
Date: Tue, 02 Mar 2021 15:46:18 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
X-XSS-Protection: 1,1; mode=block
X-Content-Type-Options: nosniff,nosniff
X-Instance-ID: 2SqoGnEiPYDM75fHH
Vary: Accept-Encoding
Content-Encoding: gzip
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Frame-Options: SAMEORIGIN

• https://185.218.72.33/
185.218.72.33
Inline-JavaScript (∑/total): 3/1265 Inline-CSS (∑/total): 1/966		200

Html is minified: 101.37 %
Other inline scripts (∑/total): 2/1265		2.343
N
Certificate error: RemoteCertificateNameMismatch
small visible content (num chars: 0)
Server: nginx
Date: Tue, 02 Mar 2021 15:46:14 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
X-XSS-Protection: 1,1; mode=block
X-Content-Type-Options: nosniff,nosniff
X-Instance-ID: 2SqoGnEiPYDM75fHH
Vary: Accept-Encoding
Content-Encoding: gzip
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Frame-Options: SAMEORIGIN

 

7. Comments


1. General Results, most used to calculate the result

Aname "chat.bakkerspees.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: 3331 (complete: 142558)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: chat.bakkerspees.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: chat.bakkerspees.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, 63072000 seconds = 730 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://chat.bakkerspees.nl/ 185.218.72.33
301
https://chat.bakkerspees.nl/
Correct redirect http - https with the same domain name
Nhttps://185.218.72.33/ 185.218.72.33
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 chat.bakkerspees.nl, 1 ip addresses, 1 different http results.

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 6 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 6 Queries complete, 6 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.ns0.transip.net (195.135.195.195, 2a01:7c8:dddd:195::195), ns1.transip.nl (195.8.195.195, 2a01:7c8:7000:195::195), ns2.transip.eu (2a01:7c8:f:c1f::195, 37.97.199.195)
AGood (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns0.transip.net, ns1.transip.nl, ns2.transip.eu, 3 Name Servers included in Delegation: ns0.transip.net, ns1.transip.nl, ns2.transip.eu, 3 Name Servers included in 1 Zone definitions: ns0.transip.net, ns1.transip.nl, ns2.transip.eu, 1 Name Servers listed in SOA.Primary: ns0.transip.net.
AGood: Only one SOA.Primary Name Server found.: ns0.transip.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns0.transip.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.
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 195., 37., 3 different subnets (first two Bytes): 195.135., 195.8., 37.97., 3 different subnets (first three Bytes): 195.135.195., 195.8.195., 37.97.199.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2a01:, 1 different subnets (first two blocks): 2a01:07c8:, 3 different subnets (first three blocks): 2a01:07c8:000f:, 2a01:07c8:7000:, 2a01:07c8:dddd:, 3 different subnets (first four blocks): 2a01:07c8:000f:0c1f:, 2a01:07c8:7000:0195:, 2a01:07c8:dddd:0195:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 12 good Nameserver
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns0.transip.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: digicert.com is allowed to create wildcard-certificates
AGood: CAA entries found, creating certificate is limited: trustproviderbv.digitalcertvalidation.com is allowed to create wildcard-certificates

4. Content- and Performance-critical Checks

https://chat.bakkerspees.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html 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://chat.bakkerspees.nl/ 185.218.72.33
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://chat.bakkerspees.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
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://185.218.72.33/ 185.218.72.33
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.
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
https://chat.bakkerspees.nl/ 185.218.72.33
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://chat.bakkerspees.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://185.218.72.33/ 185.218.72.33
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://chat.bakkerspees.nl/ 185.218.72.33
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 1 script elements without defer/async.
https://chat.bakkerspees.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 1 script elements without defer/async.
https://185.218.72.33/ 185.218.72.33
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 1 script elements without defer/async.
Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 2 external CSS / JavaScript files without GZip found - 4 with GZip, 6 complete
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 5 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 4 with Cache-Control long enough, 9 complete.
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
http://chat.bakkerspees.nl/ 185.218.72.33
301

Warning: HSTS header sent via http has no effect
ADuration: 94523 milliseconds, 94.523 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
chat.bakkerspees.nl
185.218.72.33
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
chat.bakkerspees.nl
185.218.72.33
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)

1CN=*.bakkerspees.nl


2CN=Trust Provider B.V. TLS RSA CA G1, OU=Domain Validated SSL, O=Trust Provider B.V., C=NL


chat.bakkerspees.nl
chat.bakkerspees.nl
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

chat.bakkerspees.nl
chat.bakkerspees.nl
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)

1CN=*.bakkerspees.nl


2CN=Trust Provider B.V. TLS RSA CA G1, OU=Domain Validated SSL, O=Trust Provider B.V., C=NL


185.218.72.33
185.218.72.33
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

185.218.72.33
185.218.72.33
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
Chain (complete)

1CN=*.bakkerspees.nl


2CN=Trust Provider B.V. TLS RSA CA G1, OU=Domain Validated SSL, O=Trust Provider B.V., C=NL

 

9. Certificates

1.
1.
CN=*.bakkerspees.nl
05.01.2021
22.01.2022
1055 days expired		*.bakkerspees.nl, bakkerspees.nl - 2 entries
1.
1.
CN=*.bakkerspees.nl
05.01.2021

22.01.2022
1055 days expired


*.bakkerspees.nl, bakkerspees.nl - 2 entries

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:09A45222C1B11E9F711ED2DDEFB7AA9C
Thumbprint:5B0BAE6227DBFE3D16988F5C35F04B7FB3284871
SHA256 / Certificate:jBG+rCfuVWMVfybZD9F84YxBMtAvampnHnF6orT458w=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d7ac717cf975cc7434b223dfb010c5c0fb4f4a9b2940b53bc419a14f1447676
SHA256 hex / Subject Public Key Information (SPKI):8d7ac717cf975cc7434b223dfb010c5c0fb4f4a9b2940b53bc419a14f1447676
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://statusd.digitalcertvalidation.com
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=Trust Provider B.V. TLS RSA CA G1, OU=Domain Validated SSL, O=Trust Provider B.V., C=NL
02.11.2017
02.11.2027
expires in 1055 days

2.
CN=Trust Provider B.V. TLS RSA CA G1, OU=Domain Validated SSL, O=Trust Provider B.V., C=NL
02.11.2017

02.11.2027
expires in 1055 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0EC411EDF002F73036C4E5D42F3E34F2
Thumbprint:30B35A6F8631A1E1E00E4CE44783469938A31F13
SHA256 / Certificate:AJhxw6TGBzEeWukvAQlfm/dhALh5SrCppSEOZ5TIYHw=
SHA256 hex / Cert (DANE * 0 1):009871c3a4c607311e5ae92f01095f9bf76100b8794ab0a9a5210e6794c8607c
SHA256 hex / PublicKey (DANE * 1 1):0d9d82348708a998f76ab3a0e1da98da793144f253472a4b71330dfc56c664b3
SHA256 hex / Subject Public Key Information (SPKI):0d9d82348708a998f76ab3a0e1da98da793144f253472a4b71330dfc56c664b3
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.digicert.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)




3.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
01.08.2013
15.01.2038
expires in 4782 days

3.
CN=DigiCert Global Root G2, OU=www.digicert.com, O=DigiCert Inc, C=US
01.08.2013

15.01.2038
expires in 4782 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:033AF1E6A711A9A0BB2864B11D09FAE5
Thumbprint:DF3C24F9BFD666761B268073FE06D1CC8D4F82A4
SHA256 / Certificate:yzzLt2Ax5eATj43TmiP53kf/w15DwRRM6ifUalqxy18=
SHA256 hex / Cert (DANE * 0 1):cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
SHA256 hex / PublicKey (DANE * 1 1):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
SHA256 hex / Subject Public Key Information (SPKI):8bb593a93be1d0e8a822bb887c547890c3e706aad2dab76254f97fb36b82fc26
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

No data found or small Code-update

 

Details

Small Code Update - wait one minute

 

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: ns0.transip.net, ns1.transip.nl, ns2.transip.eu

 

QNr.DomainTypeNS used
1
net
NS
f.root-servers.net (2001:500:2f::f)

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
ns0.transip.net: 195.135.195.195, 2a01:7c8:dddd:195::195
NS
a.gtld-servers.net (2001:503:a83e::2:30)
3
nl
NS
e.root-servers.net (2001:500:a8::e)

Answer: ns1.dns.nl, ns2.dns.nl, ns3.dns.nl
4
ns1.transip.nl: 195.8.195.195, 2a01:7c8:7000:195::195
NS
ns1.dns.nl (2001:678:2c:0:194:0:28:53)
5
eu
NS
d.root-servers.net (2001:500:2d::d)

Answer: nl.dns.eu, si.dns.eu, w.dns.eu, x.dns.eu, y.dns.eu
6
ns2.transip.eu: 2a01:7c8:f:c1f::195, 37.97.199.195
NS
si.dns.eu (2001:1470:8000:100::1)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
proxy.bakkerspees.nl
0

no CAA entry found
1
0
chat.bakkerspees.nl



1
0
bakkerspees.nl
5
issue
digicert.com
1
0

5
issue
digicert.com
1
0

9
issuewild
digicert.com
1
0

9
issuewild
digicert.com
1
0

5
issue
letsencrypt.org
1
0

5
issue
letsencrypt.org
1
0

9
issuewild
trustproviderbv.digitalcertvalidation.com
1
0

9
issuewild
trustproviderbv.digitalcertvalidation.com
1
0
nl
0

no CAA entry found
1
0

0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bakkerspees.nl
v=spf1 mx a ip4:46.231.86.250/32 ip4:185.218.72.0/22 ip4:83.98.175.48/28 ip6:2a0a:1880::/56 ?all
ok
1
0
chat.bakkerspees.nl


1
0
_acme-challenge.chat.bakkerspees.nl

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

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

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

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

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=ecf10592-c2f6-4053-bb60-bfd6a299dfd4

 

Last Result: https://check-your-website.server-daten.de/?q=chat.bakkerspees.nl - 2021-03-02 16:45:23

 

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

 

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