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




P

Tls-Protocol error

Checked:
20.11.2023 19:38:08


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
spitzbuwe.de
A
89.58.15.224
Nuremberg/Bavaria/Germany (DE) - netcup GmbH
Hostname: mail.zupmail.de
yes
1
0

AAAA

yes


www.spitzbuwe.de
A
89.58.15.224
Nuremberg/Bavaria/Germany (DE) - netcup GmbH
Hostname: mail.zupmail.de
yes
1
0

AAAA

yes


*.spitzbuwe.de
A
89.58.15.224
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 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 46780, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2023, 00:00:00 +, Signature-Inception: 20.11.2023, 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: de
de
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 26755, DigestType 2 and Digest 80E1eAmllUMRzLgq3hFMbB1ySnXAOVE3qjl4A1Ql540=



1 RRSIG RR to validate DS RR found



RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.12.2023, 05:00:00 +, Signature-Inception: 20.11.2023, 04:00:00 +, KeyTag 46780, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 10209, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.11.2023, 23:44:41 +, Signature-Inception: 16.11.2023, 22:14:41 +, KeyTag 26755, Signer-Name: de



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



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

Zone: spitzbuwe.de
spitzbuwe.de
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 29381, DigestType 2 and Digest qjUYq5bxLeUDkp5SZpNoqSi1KJQy4kyMQ3vmSAeBblA=



1 RRSIG RR to validate DS RR found



RRSIG-Owner spitzbuwe.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.12.2023, 06:57:50 +, Signature-Inception: 18.11.2023, 05:27:50 +, KeyTag 10209, Signer-Name: de



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 22213, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner spitzbuwe.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



RRSIG-Owner spitzbuwe.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 29381, Signer-Name: spitzbuwe.de



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



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



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



RRSIG Type 1 validates the A - Result: 89.58.15.224
Validated: RRSIG-Owner spitzbuwe.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



RRSIG Type 16 validates the TXT - Result: v=spf1 a:mail.zupmail.de mx ?all
Validated: RRSIG-Owner spitzbuwe.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "3otqi5af07br1g70lsar0187bhmtq4pq" equal the hashed NSEC3-owner "3otqi5af07br1g70lsar0187bhmtq4pq" and the hashed NextOwner "60g9taqghel02d148act86tk109luu86". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "3otqi5af07br1g70lsar0187bhmtq4pq" equal the hashed NSEC3-owner "3otqi5af07br1g70lsar0187bhmtq4pq" and the hashed NextOwner "60g9taqghel02d148act86tk109luu86". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.spitzbuwe.de) sends a valid NSEC3 RR as result with the hashed owner name "mdmgu6kimksiq5e38ptkb2h4824n2hv0" (unhashed: _tcp.spitzbuwe.de). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner mdmgu6kimksiq5e38ptkb2h4824n2hv0.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



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 "5m4c1e7mfmcgs3ppkikt74lfton65aqo" (unhashed: *._tcp.spitzbuwe.de) with the owner "3otqi5af07br1g70lsar0187bhmtq4pq" and the NextOwner "60g9taqghel02d148act86tk109luu86". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NXDomain-Proof required and found.



TLSA-Query (_443._tcp.spitzbuwe.de) sends a valid NSEC3 RR as result with the hashed query name "q8nh0d6uh7hpkuhav581hbqkdo1hcjlt" between the hashed NSEC3-owner "otvtq446m35nljqa9vore94pk9fk09ph" and the hashed NextOwner "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner otvtq446m35nljqa9vore94pk9fk09ph.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "3otqi5af07br1g70lsar0187bhmtq4pq" equal the hashed NSEC3-owner "3otqi5af07br1g70lsar0187bhmtq4pq" and the hashed NextOwner "60g9taqghel02d148act86tk109luu86". 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, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.

Zone: www.spitzbuwe.de
www.spitzbuwe.de
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "3otqi5af07br1g70lsar0187bhmtq4pq" as Owner. That's the Hash of "spitzbuwe.de" with the NextHashedOwnerName "60g9taqghel02d148act86tk109luu86". So that domain name is the Closest Encloser of "www.spitzbuwe.de". Opt-Out: False.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



The ClosestEncloser says, that "*.spitzbuwe.de" with the Hash "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" 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 "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" and the Next Owner "3ortvlcnbchh03oc7g3ujlao75edp7lr", 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: A, RRSIG Validated: RRSIG-Owner tdt0vo0s2k1pt19a2hcs4fhmpp28dofo.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



RRSIG Type 1 validates the A - Result: 89.58.15.224. RRSIG Owner has 3 labels, RRSIG Labels = 2, so it's a wildcard expansion, the Query Name doesn't exists. An additional NSEC/NSEC3 is required to confirm the Not-Existence of the query name.
Validated: RRSIG-Owner www.spitzbuwe.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



A-Query sends a valid NSEC3 RR as result with the hashed owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" (unhashed: *.spitzbuwe.de) as the Wildcard-Expansion of the Closest Encloser of the query name "um50s1l4g85klm6bpo7pf5gis7q8llrd". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). A-Query sends a valid NSEC3 RR as result with the owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" greater the NextOwner-Name "3ortvlcnbchh03oc7g3ujlao75edp7lr", so the NSEC3 covers the end of the zone. The hashed query name "um50s1l4g85klm6bpo7pf5gis7q8llrd" comes after the hashed Owner, so the zone confirmes the not-existence of that A RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner tdt0vo0s2k1pt19a2hcs4fhmpp28dofo.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "3otqi5af07br1g70lsar0187bhmtq4pq" (unhashed: spitzbuwe.de). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" (unhashed: *.spitzbuwe.de) as the Wildcard-Expansion of the Closest Encloser of the query name "um50s1l4g85klm6bpo7pf5gis7q8llrd". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). CNAME-Query sends a valid NSEC3 RR as result with the owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" greater the NextOwner-Name "3ortvlcnbchh03oc7g3ujlao75edp7lr", so the NSEC3 covers the end of the zone. The hashed query name "um50s1l4g85klm6bpo7pf5gis7q8llrd" comes after the hashed Owner, so the zone confirmes the not-existence of that CNAME RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner tdt0vo0s2k1pt19a2hcs4fhmpp28dofo.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "3otqi5af07br1g70lsar0187bhmtq4pq" (unhashed: spitzbuwe.de). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" (unhashed: *.spitzbuwe.de) as the Wildcard-Expansion of the Closest Encloser of the query name "um50s1l4g85klm6bpo7pf5gis7q8llrd". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). TXT-Query sends a valid NSEC3 RR as result with the owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" greater the NextOwner-Name "3ortvlcnbchh03oc7g3ujlao75edp7lr", so the NSEC3 covers the end of the zone. The hashed query name "um50s1l4g85klm6bpo7pf5gis7q8llrd" comes after the hashed Owner, so the zone confirmes the not-existence of that TXT RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner tdt0vo0s2k1pt19a2hcs4fhmpp28dofo.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "3otqi5af07br1g70lsar0187bhmtq4pq" (unhashed: spitzbuwe.de). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" (unhashed: *.spitzbuwe.de) as the Wildcard-Expansion of the Closest Encloser of the query name "um50s1l4g85klm6bpo7pf5gis7q8llrd". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). AAAA-Query sends a valid NSEC3 RR as result with the owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" greater the NextOwner-Name "3ortvlcnbchh03oc7g3ujlao75edp7lr", so the NSEC3 covers the end of the zone. The hashed query name "um50s1l4g85klm6bpo7pf5gis7q8llrd" comes after the hashed Owner, so the zone confirmes the not-existence of that AAAA RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner tdt0vo0s2k1pt19a2hcs4fhmpp28dofo.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.www.spitzbuwe.de) sends a valid NSEC3 RR as result with the hashed owner name "3otqi5af07br1g70lsar0187bhmtq4pq" (unhashed: spitzbuwe.de). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "um50s1l4g85klm6bpo7pf5gis7q8llrd" (unhashed: www.spitzbuwe.de) with the owner "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" and the NextOwner "3ortvlcnbchh03oc7g3ujlao75edp7lr". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" (unhashed: *.spitzbuwe.de) as the Wildcard-Expansion of the Closest Encloser of the query name "h0gb9g1mg10a6ci429q493ur84dclb0h". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: A, RRSIG Validated: RRSIG-Owner tdt0vo0s2k1pt19a2hcs4fhmpp28dofo.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "3otqi5af07br1g70lsar0187bhmtq4pq" (unhashed: spitzbuwe.de). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3otqi5af07br1g70lsar0187bhmtq4pq.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" (unhashed: *.spitzbuwe.de) as the Wildcard-Expansion of the Closest Encloser of the query name "um50s1l4g85klm6bpo7pf5gis7q8llrd". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). CAA-Query sends a valid NSEC3 RR as result with the owner name "tdt0vo0s2k1pt19a2hcs4fhmpp28dofo" greater the NextOwner-Name "3ortvlcnbchh03oc7g3ujlao75edp7lr", so the NSEC3 covers the end of the zone. The hashed query name "um50s1l4g85klm6bpo7pf5gis7q8llrd" comes after the hashed Owner, so the zone confirmes the not-existence of that CAA RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner tdt0vo0s2k1pt19a2hcs4fhmpp28dofo.spitzbuwe.de., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 20.12.2023, 19:30:00 +, Signature-Inception: 19.11.2023, 19:30:00 +, KeyTag 22213, Signer-Name: spitzbuwe.de



Status: Good. NoData-Proof required and found.


3. Name Servers

DomainNameserverNS-IP
www.spitzbuwe.de
  root-dns.netcup.net

spitzbuwe.de
  root-dns.netcup.net
46.38.225.225
Karlsruhe/Baden-Wurttemberg/Germany (DE) - netcup GmbH


 
2a03:4000:0:1::e1e1
Karlsruhe/Baden-Wurttemberg/Germany (DE) - netcup GmbH


  second-dns.netcup.net
37.221.199.199
Karlsruhe/Baden-Wurttemberg/Germany (DE) - netcup GmbH


 
2a03:4000:2:24b::c7c7
Karlsruhe/Baden-Wurttemberg/Germany (DE) - netcup GmbH


  third-dns.netcup.net
188.68.63.68
Karlsruhe/Baden-Wurttemberg/Germany (DE) - netcup GmbH


 
2a03:4001:0:106::3f44
Karlsruhe/Baden-Wurttemberg/Germany (DE) - netcup GmbH

de
  a.nic.de / ns-2.de.nl1.bind


  f.nic.de / ns-2.de.de1


  l.de.net / ns-1.de.uk1


  n.de.net / s3.amx


  s.de.net / ns-2.de.de9


  z.nic.de / ns-1.de.de2.bind


4. SOA-Entries


Domain:de
Zone-Name:de
Primary:f.nic.de
Mail:dns-operations.denic.de
Serial:1700505331
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:1


Domain:de
Zone-Name:de
Primary:f.nic.de
Mail:dns-operations.denic.de
Serial:1700505428
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:5


Domain:spitzbuwe.de
Zone-Name:spitzbuwe.de
Primary:root-dns.netcup.net
Mail:dnsadmin.netcup.net
Serial:2023112084
Refresh:28800
Retry:7200
Expire:1209600
TTL:86400
num Entries:6


Domain:www.spitzbuwe.de
Zone-Name:spitzbuwe.de
Primary:root-dns.netcup.net
Mail:dnsadmin.netcup.net
Serial:2023112084
Refresh:28800
Retry:7200
Expire:1209600
TTL:86400
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://spitzbuwe.de/
89.58.15.224 GZip used - 556 / 1033 - 46.18 %
200

Html is minified: 135.03 %
0.047
H
small visible content (num chars: 228)
Congratulations! You've successfully started the Nginx Proxy Manager. If you're seeing this site then you're trying to access a host that isn't set up yet. Log in to the Admin panel to get started. Powered by Nginx Proxy Manager
Server: openresty
Date: Mon, 20 Nov 2023 18:38:48 GMT
Content-Type: text/html
Last-Modified: Mon, 14 Aug 2023 23:13:21 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"64dab511-409"
Content-Encoding: gzip

• http://www.spitzbuwe.de/
89.58.15.224 GZip used - 556 / 1033 - 46.18 %
200

Html is minified: 135.03 %
0.047
H
small visible content (num chars: 228)
Congratulations! You've successfully started the Nginx Proxy Manager. If you're seeing this site then you're trying to access a host that isn't set up yet. Log in to the Admin panel to get started. Powered by Nginx Proxy Manager
Server: openresty
Date: Mon, 20 Nov 2023 18:38:48 GMT
Content-Type: text/html
Last-Modified: Mon, 14 Aug 2023 23:13:21 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"64dab511-409"
Content-Encoding: gzip

• https://spitzbuwe.de/
89.58.15.224
-10

0.047
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://www.spitzbuwe.de/
89.58.15.224
-10

0.047
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• http://spitzbuwe.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
89.58.15.224 GZip used - 111 / 150 - 26.00 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.29 %
0.063
A
Not Found
Visible Content: 404 Not Found openresty
Server: openresty
Date: Mon, 20 Nov 2023 18:38:48 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• http://www.spitzbuwe.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
89.58.15.224 GZip used - 111 / 150 - 26.00 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.29 %
0.030
A
Not Found
Visible Content: 404 Not Found openresty
Server: openresty
Date: Mon, 20 Nov 2023 18:38:48 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://89.58.15.224/
89.58.15.224
-10

0.046
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

7. Comments


1. General Results, most used to calculate the result

Aname "spitzbuwe.de" is domain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 9157 (complete: 231048)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: spitzbuwe.de has only one ip address.
Warning: Only one ip address found: www.spitzbuwe.de 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: spitzbuwe.de has no ipv6 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: www.spitzbuwe.de has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (4 urls)
http://spitzbuwe.de/ 89.58.15.224


Url with incomplete Content-Type - header - missing charset
http://www.spitzbuwe.de/ 89.58.15.224


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


Url with incomplete Content-Type - header - missing charset
http://www.spitzbuwe.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 89.58.15.224


Url with incomplete Content-Type - header - missing charset
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Phttps://spitzbuwe.de/ 89.58.15.224
-10

Error creating a TLS-Connection: No more details available.
Phttps://www.spitzbuwe.de/ 89.58.15.224
-10

Error creating a TLS-Connection: No more details available.
Phttps://89.58.15.224/ 89.58.15.224
-10

Error creating a TLS-Connection: No more details available.
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 spitzbuwe.de, 1 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.spitzbuwe.de, 1 ip addresses.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.spitzbuwe.de

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:: 12 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 12 Queries complete, 12 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net, 3 Name Servers included in Delegation: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net, 3 Name Servers included in 1 Zone definitions: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net, 1 Name Servers listed in SOA.Primary: root-dns.netcup.net.
AGood: Only one SOA.Primary Name Server found.: root-dns.netcup.net.
AGood: SOA.Primary Name Server included in the delegation set.: root-dns.netcup.net.
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: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.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: 3 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 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: netcup.net
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: DE
AInfo: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 188., 37., 46., 3 different subnets (first two Bytes): 188.68., 37.221., 46.38., 3 different subnets (first three Bytes): 188.68.63., 37.221.199., 46.38.225.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2a03:, 2 different subnets (first two blocks): 2a03:4000:, 2a03:4001:, 3 different subnets (first three blocks): 2a03:4000:0000:, 2a03:4000:0002:, 2a03:4001:0000:, 3 different subnets (first four blocks): 2a03:4000:0000:0001:, 2a03:4000:0002:024b:, 2a03:4001:0000:0106:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
AGood: All SOA have the same Serial Number
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.
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: 52803 milliseconds, 52.803 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)

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net

QNr.DomainTypeNS used
1
net
NS
e.root-servers.net (2001:500:a8::e)

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
root-dns.netcup.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: acns01.xaas.systems, acns02.xaas.systems, acns03.xaas.systems, acns04.xaas.systems, acns05.xaas.systems
3
second-dns.netcup.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: acns01.xaas.systems, acns02.xaas.systems, acns03.xaas.systems, acns04.xaas.systems, acns05.xaas.systems
4
third-dns.netcup.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: acns01.xaas.systems, acns02.xaas.systems, acns03.xaas.systems, acns04.xaas.systems, acns05.xaas.systems
5
systems
NS
b.root-servers.net (2001:500:200::b)

Answer: v0n0.nic.systems, v0n1.nic.systems, v0n2.nic.systems, v0n3.nic.systems, v2n0.nic.systems, v2n1.nic.systems
6
acns01.xaas.systems: 217.146.18.1, 2a00:11c0:aa1::1
NS
v0n0.nic.systems (2a01:8840:16::38)

Answer: acns05.xaas.systems
185.81.208.1, 2a00:11c0:1010::1

Answer: acns04.xaas.systems
213.227.191.1, 2803:ad80:aa1::1

Answer: acns03.xaas.systems
213.227.160.1, 2605:380:aa1::1

Answer: acns02.xaas.systems
188.172.248.1, 2a05:8900:aa1::1
7
root-dns.netcup.net: 46.38.225.225
A
acns01.xaas.systems (2a00:11c0:aa1::1)
8
root-dns.netcup.net: 2a03:4000:0:1::e1e1
AAAA
acns01.xaas.systems (2a00:11c0:aa1::1)
9
second-dns.netcup.net: 37.221.199.199
A
acns01.xaas.systems (2a00:11c0:aa1::1)
10
second-dns.netcup.net: 2a03:4000:2:24b::c7c7
AAAA
acns01.xaas.systems (2a00:11c0:aa1::1)
11
third-dns.netcup.net: 188.68.63.68
A
acns01.xaas.systems (2a00:11c0:aa1::1)
12
third-dns.netcup.net: 2a03:4001:0:106::3f44
AAAA
acns01.xaas.systems (2a00:11c0:aa1::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.spitzbuwe.de
0

no CAA entry found
1
0
spitzbuwe.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
spitzbuwe.de
v=spf1 a:mail.zupmail.de mx ?all
ok
1
0
www.spitzbuwe.de

ok
1
0
_acme-challenge.spitzbuwe.de

missing entry or wrong length
1
0
_acme-challenge.www.spitzbuwe.de

missing entry or wrong length
1
0
_acme-challenge.spitzbuwe.de.spitzbuwe.de

perhaps wrong
1
0
_acme-challenge.www.spitzbuwe.de.spitzbuwe.de

perhaps wrong
1
0
_acme-challenge.www.spitzbuwe.de.www.spitzbuwe.de

perhaps wrong
1
0


15. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

spitzbuwe.de
10
mail.zupmail.de
01ok

A


89.58.15.224
01ok

AAAA


2a03:4000:60:e4f:9417:b4ff:fe07:d8ef
01ok

CNAME


00ok
_dmarc
TXT
_dmarc.spitzbuwe.de

v=DMARC1;p=none;rua=mailto:postmaster@spitzbuwe.de;ruf=mailto:postmaster@spitzbuwe.de
01ok



16. Cipher Suites

No results


17. Portchecks

DomainIPPortDescriptionResultAnswer
spitzbuwe.de
89.58.15.224
21
FTP



spitzbuwe.de
89.58.15.224
21
FTP



spitzbuwe.de
89.58.15.224
22
SSH
open
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u1

spitzbuwe.de
89.58.15.224
22
SSH
open
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u1
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
spitzbuwe.de IN SSHFP 3 2 83dea1520d5b4ab2011cb173b0f6b42e63e0056dcee0d19b3e486bb80c6c1bb7
spitzbuwe.de IN SSHFP 4 2 be1b4b9c2a5550470da48e1b8157f92b8d365fd963c7d73a6a488328142d359e
spitzbuwe.de
89.58.15.224
25
SMTP



spitzbuwe.de
89.58.15.224
25
SMTP



spitzbuwe.de
89.58.15.224
53
DNS



spitzbuwe.de
89.58.15.224
53
DNS



spitzbuwe.de
89.58.15.224
110
POP3



spitzbuwe.de
89.58.15.224
110
POP3



spitzbuwe.de
89.58.15.224
143
IMAP



spitzbuwe.de
89.58.15.224
143
IMAP



spitzbuwe.de
89.58.15.224
465
SMTP (encrypted)



spitzbuwe.de
89.58.15.224
465
SMTP (encrypted)



spitzbuwe.de
89.58.15.224
587
SMTP (encrypted, submission)



spitzbuwe.de
89.58.15.224
587
SMTP (encrypted, submission)



spitzbuwe.de
89.58.15.224
993
IMAP (encrypted)



spitzbuwe.de
89.58.15.224
993
IMAP (encrypted)



spitzbuwe.de
89.58.15.224
995
POP3 (encrypted)



spitzbuwe.de
89.58.15.224
995
POP3 (encrypted)



spitzbuwe.de
89.58.15.224
1433
MS SQL



spitzbuwe.de
89.58.15.224
1433
MS SQL



spitzbuwe.de
89.58.15.224
2082
cPanel (http)



spitzbuwe.de
89.58.15.224
2082
cPanel (http)



spitzbuwe.de
89.58.15.224
2083
cPanel (https)



spitzbuwe.de
89.58.15.224
2083
cPanel (https)



spitzbuwe.de
89.58.15.224
2086
WHM (http)



spitzbuwe.de
89.58.15.224
2086
WHM (http)



spitzbuwe.de
89.58.15.224
2087
WHM (https)



spitzbuwe.de
89.58.15.224
2087
WHM (https)



spitzbuwe.de
89.58.15.224
2089
cPanel Licensing



spitzbuwe.de
89.58.15.224
2089
cPanel Licensing



spitzbuwe.de
89.58.15.224
2095
cPanel Webmail (http)



spitzbuwe.de
89.58.15.224
2095
cPanel Webmail (http)



spitzbuwe.de
89.58.15.224
2096
cPanel Webmail (https)



spitzbuwe.de
89.58.15.224
2096
cPanel Webmail (https)



spitzbuwe.de
89.58.15.224
2222
DirectAdmin (http)



spitzbuwe.de
89.58.15.224
2222
DirectAdmin (http)



spitzbuwe.de
89.58.15.224
2222
DirectAdmin (https)



spitzbuwe.de
89.58.15.224
2222
DirectAdmin (https)



spitzbuwe.de
89.58.15.224
3306
mySql



spitzbuwe.de
89.58.15.224
3306
mySql



spitzbuwe.de
89.58.15.224
5224
Plesk Licensing



spitzbuwe.de
89.58.15.224
5224
Plesk Licensing



spitzbuwe.de
89.58.15.224
5432
PostgreSQL



spitzbuwe.de
89.58.15.224
5432
PostgreSQL



spitzbuwe.de
89.58.15.224
8080
Ookla Speedtest (http)



spitzbuwe.de
89.58.15.224
8080
Ookla Speedtest (http)



spitzbuwe.de
89.58.15.224
8080
Ookla Speedtest (https)



spitzbuwe.de
89.58.15.224
8080
Ookla Speedtest (https)



spitzbuwe.de
89.58.15.224
8083
VestaCP http



spitzbuwe.de
89.58.15.224
8083
VestaCP http



spitzbuwe.de
89.58.15.224
8083
VestaCP https



spitzbuwe.de
89.58.15.224
8083
VestaCP https



spitzbuwe.de
89.58.15.224
8443
Plesk Administration (https)



spitzbuwe.de
89.58.15.224
8443
Plesk Administration (https)



spitzbuwe.de
89.58.15.224
8447
Plesk Installer + Updates



spitzbuwe.de
89.58.15.224
8447
Plesk Installer + Updates



spitzbuwe.de
89.58.15.224
8880
Plesk Administration (http)



spitzbuwe.de
89.58.15.224
8880
Plesk Administration (http)



spitzbuwe.de
89.58.15.224
10000
Webmin (http)



spitzbuwe.de
89.58.15.224
10000
Webmin (http)



spitzbuwe.de
89.58.15.224
10000
Webmin (https)



spitzbuwe.de
89.58.15.224
10000
Webmin (https)



www.spitzbuwe.de
89.58.15.224
21
FTP



www.spitzbuwe.de
89.58.15.224
21
FTP



www.spitzbuwe.de
89.58.15.224
22
SSH
open
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u1

www.spitzbuwe.de
89.58.15.224
22
SSH
open
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u1
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
www.spitzbuwe.de IN SSHFP 3 2 83dea1520d5b4ab2011cb173b0f6b42e63e0056dcee0d19b3e486bb80c6c1bb7
www.spitzbuwe.de IN SSHFP 4 2 be1b4b9c2a5550470da48e1b8157f92b8d365fd963c7d73a6a488328142d359e
www.spitzbuwe.de
89.58.15.224
25
SMTP



www.spitzbuwe.de
89.58.15.224
25
SMTP



www.spitzbuwe.de
89.58.15.224
53
DNS



www.spitzbuwe.de
89.58.15.224
53
DNS



www.spitzbuwe.de
89.58.15.224
110
POP3



www.spitzbuwe.de
89.58.15.224
110
POP3



www.spitzbuwe.de
89.58.15.224
143
IMAP



www.spitzbuwe.de
89.58.15.224
143
IMAP



www.spitzbuwe.de
89.58.15.224
465
SMTP (encrypted)



www.spitzbuwe.de
89.58.15.224
465
SMTP (encrypted)



www.spitzbuwe.de
89.58.15.224
587
SMTP (encrypted, submission)



www.spitzbuwe.de
89.58.15.224
587
SMTP (encrypted, submission)



www.spitzbuwe.de
89.58.15.224
993
IMAP (encrypted)



www.spitzbuwe.de
89.58.15.224
993
IMAP (encrypted)



www.spitzbuwe.de
89.58.15.224
995
POP3 (encrypted)



www.spitzbuwe.de
89.58.15.224
995
POP3 (encrypted)



www.spitzbuwe.de
89.58.15.224
1433
MS SQL



www.spitzbuwe.de
89.58.15.224
1433
MS SQL



www.spitzbuwe.de
89.58.15.224
2082
cPanel (http)



www.spitzbuwe.de
89.58.15.224
2082
cPanel (http)



www.spitzbuwe.de
89.58.15.224
2083
cPanel (https)



www.spitzbuwe.de
89.58.15.224
2083
cPanel (https)



www.spitzbuwe.de
89.58.15.224
2086
WHM (http)



www.spitzbuwe.de
89.58.15.224
2086
WHM (http)



www.spitzbuwe.de
89.58.15.224
2087
WHM (https)



www.spitzbuwe.de
89.58.15.224
2087
WHM (https)



www.spitzbuwe.de
89.58.15.224
2089
cPanel Licensing



www.spitzbuwe.de
89.58.15.224
2089
cPanel Licensing



www.spitzbuwe.de
89.58.15.224
2095
cPanel Webmail (http)



www.spitzbuwe.de
89.58.15.224
2095
cPanel Webmail (http)



www.spitzbuwe.de
89.58.15.224
2096
cPanel Webmail (https)



www.spitzbuwe.de
89.58.15.224
2096
cPanel Webmail (https)



www.spitzbuwe.de
89.58.15.224
2222
DirectAdmin (http)



www.spitzbuwe.de
89.58.15.224
2222
DirectAdmin (http)



www.spitzbuwe.de
89.58.15.224
2222
DirectAdmin (https)



www.spitzbuwe.de
89.58.15.224
2222
DirectAdmin (https)



www.spitzbuwe.de
89.58.15.224
3306
mySql



www.spitzbuwe.de
89.58.15.224
3306
mySql



www.spitzbuwe.de
89.58.15.224
5224
Plesk Licensing



www.spitzbuwe.de
89.58.15.224
5224
Plesk Licensing



www.spitzbuwe.de
89.58.15.224
5432
PostgreSQL



www.spitzbuwe.de
89.58.15.224
5432
PostgreSQL



www.spitzbuwe.de
89.58.15.224
8080
Ookla Speedtest (http)



www.spitzbuwe.de
89.58.15.224
8080
Ookla Speedtest (http)



www.spitzbuwe.de
89.58.15.224
8080
Ookla Speedtest (https)



www.spitzbuwe.de
89.58.15.224
8080
Ookla Speedtest (https)



www.spitzbuwe.de
89.58.15.224
8083
VestaCP http



www.spitzbuwe.de
89.58.15.224
8083
VestaCP http



www.spitzbuwe.de
89.58.15.224
8083
VestaCP https



www.spitzbuwe.de
89.58.15.224
8083
VestaCP https



www.spitzbuwe.de
89.58.15.224
8443
Plesk Administration (https)



www.spitzbuwe.de
89.58.15.224
8443
Plesk Administration (https)



www.spitzbuwe.de
89.58.15.224
8447
Plesk Installer + Updates



www.spitzbuwe.de
89.58.15.224
8447
Plesk Installer + Updates



www.spitzbuwe.de
89.58.15.224
8880
Plesk Administration (http)



www.spitzbuwe.de
89.58.15.224
8880
Plesk Administration (http)



www.spitzbuwe.de
89.58.15.224
10000
Webmin (http)



www.spitzbuwe.de
89.58.15.224
10000
Webmin (http)



www.spitzbuwe.de
89.58.15.224
10000
Webmin (https)



www.spitzbuwe.de
89.58.15.224
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=4bab50db-43b7-4a83-975d-0937bc83b4b1


Last Result: https://check-your-website.server-daten.de/?q=spitzbuwe.de - 2023-11-20 19:38:08


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

<a href="https://check-your-website.server-daten.de/?q=spitzbuwe.de" target="_blank">Check this Site: spitzbuwe.de</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro