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

0 in Queue, 0 of max. 8 Checks (00:38:38)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

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

 

X

 

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

 

Checked:
14.01.2025 10:40:33

 

Older results

 

X - 14.01.2025 08:03:55
I - 10.01.2025 19:56:42
I - 10.01.2025 14:33:56

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
asdfghasdfgh.de
A
46.23.93.30
Amsterdam/North Holland/The Netherlands (NL) - High5! B.V.
Hostname: ns1.asdfghasdfgh.de
yes
2
0

AAAA
2a03:6000:93f1:620::30
Utrecht/The Netherlands (NL) - High5! B.V.

yes


www.asdfghasdfgh.de
A
46.23.93.30
Amsterdam/North Holland/The Netherlands (NL) - High5! B.V.
Hostname: ns1.asdfghasdfgh.de
yes
2
0

AAAA
2a03:6000:93f1:620::30
Utrecht/The Netherlands (NL) - High5! B.V.

yes


*.asdfghasdfgh.de
A
Name Error
yes



A
Name Error
yes



AAAA
Name Error
yes



AAAA
Name Error
yes



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






Public Key with Algorithm 8, KeyTag 26470, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2025, 00:00:00 +, Signature-Inception: 11.01.2025, 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: 27.01.2025, 05:00:00 +, Signature-Inception: 14.01.2025, 04:00:00 +, KeyTag 26470, Signer-Name: (root)






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 22128, Flags 256






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






Public Key with Algorithm 8, KeyTag 63483, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2025, 19:09:33 +, Signature-Inception: 13.01.2025, 17:39:33 +, 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: asdfghasdfgh.de

asdfghasdfgh.de
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 "vqrtfg1fsorlrv9mlg1r8119so0640l3" between the hashed NSEC3-owner "vqrqpnvjh6q5sdt1989h139u8b07u6q3" and the hashed NextOwner "vqru0lj7jj0lkpu87t4bm18igus1f3tg". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner vqrqpnvjh6q5sdt1989h139u8b07u6q3.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 22.01.2025, 10:42:55 +, Signature-Inception: 08.01.2025, 09:12:55 +, KeyTag 63483, Signer-Name: de






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tjlb7qbojvmlf1s6gdriru7vsms1lg16" as Owner. That's the Hash of "de" with the NextHashedOwnerName "tjlcsjat4ljtvo0tjncrrdf6kf6onefb". So that domain name is the Closest Encloser of "asdfghasdfgh.de". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tjlb7qbojvmlf1s6gdriru7vsms1lg16.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 22.01.2025, 10:42:55 +, Signature-Inception: 08.01.2025, 09:12:55 +, KeyTag 63483, Signer-Name: de






1 DNSKEY RR found






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner asdfghasdfgh.de., Algorithm: 13, 2 Labels, original TTL: 84600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






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






Error: DNSKEY 20741 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.






RRSIG Type 1 validates the A - Result: 46.23.93.30
Validated: RRSIG-Owner asdfghasdfgh.de., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






RRSIG Type 16 validates the TXT - Result: apple-domain=samHrkcVPZ1rTUqQ v=spf1 include:icloud.com ~all
Validated: RRSIG-Owner asdfghasdfgh.de., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






RRSIG Type 28 validates the AAAA - Result: 2A03:6000:93F1:0620:0000:0000:0000:0030
Validated: RRSIG-Owner asdfghasdfgh.de., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "9eo2qp28h4cu2b33m1v5gvrotime1cia" equal the hashed NSEC3-owner "9eo2qp28h4cu2b33m1v5gvrotime1cia" and the hashed NextOwner "bm0q5jplm8fa92tq4eropp71imnfpkhm". 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, AAAA, SSHFP, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 9eo2qp28h4cu2b33m1v5gvrotime1cia.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.asdfghasdfgh.de) sends a valid NSEC3 RR as result with the hashed owner name "9eo2qp28h4cu2b33m1v5gvrotime1cia" (unhashed: asdfghasdfgh.de). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, SSHFP, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 9eo2qp28h4cu2b33m1v5gvrotime1cia.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "m50ikaeikoogeqprhq8kqign25hkmhuu" (unhashed: _tcp.asdfghasdfgh.de) with the owner "m444f12647tccc0rjff3uospv0373kju" and the NextOwner "mbu11mqqp2cv715q3ni26qb5f4283t8q". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.asdfghasdfgh.de) sends a valid NSEC3 RR as result with the hashed query name "m6lmf0l2ofajk867ct44m8vnp3pcd4pt" between the hashed NSEC3-owner "m444f12647tccc0rjff3uospv0373kju" and the hashed NextOwner "mbu11mqqp2cv715q3ni26qb5f4283t8q". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: AAAA, RRSIG Validated: RRSIG-Owner m444f12647tccc0rjff3uospv0373kju.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.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 "do5vioakg5bapsh88fp70vk9kk6obvfr" (unhashed: *.asdfghasdfgh.de) with the owner "bu44k4ognkvar749gbodr0386cm3cd5f" and the NextOwner "fo8qbbaadnerp994ngns3a9sma9e4pvj". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner bu44k4ognkvar749gbodr0386cm3cd5f.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "9eo2qp28h4cu2b33m1v5gvrotime1cia" equal the hashed NSEC3-owner "9eo2qp28h4cu2b33m1v5gvrotime1cia" and the hashed NextOwner "bm0q5jplm8fa92tq4eropp71imnfpkhm". 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, AAAA, SSHFP, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 9eo2qp28h4cu2b33m1v5gvrotime1cia.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NoData-Proof required and found.



Zone: www.asdfghasdfgh.de

www.asdfghasdfgh.de
0 DS RR in the parent zone found






RRSIG Type 1 validates the A - Result: 46.23.93.30
Validated: RRSIG-Owner www.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






RRSIG Type 28 validates the AAAA - Result: 2A03:6000:93F1:0620:0000:0000:0000:0030
Validated: RRSIG-Owner www.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9" equal the hashed NSEC3-owner "vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9" and the hashed NextOwner "3bk3p50r8nf7699e9i1frq4j3hurs6sn". 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, AAAA, RRSIG Validated: RRSIG-Owner vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9" equal the hashed NSEC3-owner "vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9" and the hashed NextOwner "3bk3p50r8nf7699e9i1frq4j3hurs6sn". 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, AAAA, RRSIG Validated: RRSIG-Owner vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.www.asdfghasdfgh.de) sends a valid NSEC3 RR as result with the hashed owner name "vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9" (unhashed: www.asdfghasdfgh.de). So that's the Closest Encloser of the query name.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "oo4vfggjnumi19du0n7mlg5mvej0toq2" (unhashed: _tcp.www.asdfghasdfgh.de) with the owner "nr4vlrp2ru615bfqhia4at1r1gljeih9" and the NextOwner "phfpjskqajfmc55lke04rg4k86t8lgc9". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner nr4vlrp2ru615bfqhia4at1r1gljeih9.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.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 "78b6o14ra64ol20p7ktn7fes641vnu0f" (unhashed: *.www.asdfghasdfgh.de) with the owner "627tc7ucli8jd52uo3egvc0nnouqrofi" and the NextOwner "935iorq3jh9qt1djlc8783u3rf74v5nd". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner 627tc7ucli8jd52uo3egvc0nnouqrofi.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9" equal the hashed NSEC3-owner "vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9" and the hashed NextOwner "3bk3p50r8nf7699e9i1frq4j3hurs6sn". 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, AAAA, RRSIG Validated: RRSIG-Owner vhdlbu76l3k5r8tal1u6bbdvh9iu9lm9.asdfghasdfgh.de., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 09.07.2025, 00:00:00 +, Signature-Inception: 10.01.2025, 12:21:31 +, KeyTag 20741, Signer-Name: asdfghasdfgh.de






Status: Good. NoData-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
www.asdfghasdfgh.de
X  ns1.asdfghasdfgh.de

asdfghasdfgh.de
X  ns1.asdfghasdfgh.de
46.23.93.30
Amsterdam/North Holland/The Netherlands (NL) - High5! B.V.

X 
2a03:6000:93f1:620::30
Utrecht/The Netherlands (NL) - High5! B.V.

•  ns2.asdfghasdfgh.de
217.197.83.164
Berlin/Land Berlin/Germany (DE) - Individual Network Berlin e.V.		•

• 
2a0a:4580:102e::1
Berlin/Land Berlin/Germany (DE) - Individual Network Berlin e.V.		•

•  ns3.asdfghasdfgh.de
130.0.206.23
Stockholm/Stockholm County/Sweden (SE) - Adminor Aktiebolag		•

• 
2a01:7a00:adab:206::e
Stockholm/Stockholm County/Sweden (SE) - Adminor Aktiebolag		•
de
•  a.nic.de / ns-2.de.de8.knot
•

X  f.nic.de / ns-1.de.de1.knot


X  l.de.net / ns-2.de.fr1.knot


•  n.de.net / s3.amx
•

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

•  z.nic.de / ns-2.de.de2.bind
•

 

4. SOA-Entries


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


Domain:asdfghasdfgh.de
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:asdfghasdfgh.de
Zone-Name:asdfghasdfgh.de
Primary:ns1.asdfghasdfgh.de
Mail:mk.asdfghasdfgh.de
Serial:2025010203
Refresh:14400
Retry:3600
Expire:1209600
TTL:3600
num Entries:4


Domain:www.asdfghasdfgh.de
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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://asdfghasdfgh.de/
46.23.93.30
-102


1.107
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (46.23.93.30:80)

• http://asdfghasdfgh.de/
2a03:6000:93f1:620::30
-102


1.113
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. ([2a03:6000:93f1:620::30]:80)

• http://www.asdfghasdfgh.de/
46.23.93.30
-102


1.123
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (46.23.93.30:80)

• http://www.asdfghasdfgh.de/
2a03:6000:93f1:620::30
-102


1.110
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. ([2a03:6000:93f1:620::30]:80)

• https://asdfghasdfgh.de/
46.23.93.30
-102


1.133
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (46.23.93.30:443)

• https://asdfghasdfgh.de/
2a03:6000:93f1:620::30
-102


1.114
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. ([2a03:6000:93f1:620::30]:443)

• https://www.asdfghasdfgh.de/
46.23.93.30
-102


1.127
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (46.23.93.30:443)

• https://www.asdfghasdfgh.de/
2a03:6000:93f1:620::30
-102


1.120
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. ([2a03:6000:93f1:620::30]:443)

• http://asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
46.23.93.30
-102


1.130
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (46.23.93.30:80)
Visible Content:

• http://asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a03:6000:93f1:620::30
-102


1.100
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. ([2a03:6000:93f1:620::30]:80)
Visible Content:

• http://www.asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
46.23.93.30
-102


1.120
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (46.23.93.30:80)
Visible Content:

• http://www.asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a03:6000:93f1:620::30
-102


1.123
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. ([2a03:6000:93f1:620::30]:80)
Visible Content:

• https://46.23.93.30/
46.23.93.30
-102


1.120
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (46.23.93.30:443)

• https://[2a03:6000:93f1:0620:0000:0000:0000:0030]/
2a03:6000:93f1:620::30
-102


1.110
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. ([2a03:6000:93f1:620::30]:443)

 

7. Comments


1. General Results, most used to calculate the result

Aname "asdfghasdfgh.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: 10577 (complete: 263653)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: asdfghasdfgh.de has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.asdfghasdfgh.de has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: asdfghasdfgh.de has 1 ipv4, 1 ipv6 addresses
AGood: Ipv4 and Ipv6 addresses per domain name found: www.asdfghasdfgh.de has 1 ipv4, 1 ipv6 addresses
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Vhttp://asdfghasdfgh.de/ 46.23.93.30
-102

Connect failure - perhaps firewall
Vhttp://asdfghasdfgh.de/ 2a03:6000:93f1:620::30
-102

Connect failure - perhaps firewall
Vhttp://www.asdfghasdfgh.de/ 46.23.93.30
-102

Connect failure - perhaps firewall
Vhttp://www.asdfghasdfgh.de/ 2a03:6000:93f1:620::30
-102

Connect failure - perhaps firewall
Vhttps://asdfghasdfgh.de/ 46.23.93.30
-102

Connect failure - perhaps firewall
Vhttps://asdfghasdfgh.de/ 2a03:6000:93f1:620::30
-102

Connect failure - perhaps firewall
Vhttps://www.asdfghasdfgh.de/ 46.23.93.30
-102

Connect failure - perhaps firewall
Vhttps://www.asdfghasdfgh.de/ 2a03:6000:93f1:620::30
-102

Connect failure - perhaps firewall
Vhttp://asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.23.93.30
-102

Connect failure - perhaps firewall
Vhttp://asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:6000:93f1:620::30
-102

Connect failure - perhaps firewall
Vhttp://www.asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.23.93.30
-102

Connect failure - perhaps firewall
Vhttp://www.asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:6000:93f1:620::30
-102

Connect failure - perhaps firewall
Vhttps://46.23.93.30/ 46.23.93.30
-102

Connect failure - perhaps firewall
Vhttps://[2a03:6000:93f1:0620:0000:0000:0000:0030]/ 2a03:6000:93f1:620::30
-102

Connect failure - perhaps firewall
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: f.nic.de: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
XFatal error: Nameserver doesn't support TCP connection: l.de.net: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
XFatal error: Nameserver doesn't support TCP connection: ns1.asdfghasdfgh.de: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.asdfghasdfgh.de / 46.23.93.30: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.asdfghasdfgh.de / 2a03:6000:93f1:620::30: Timeout
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain asdfghasdfgh.de, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.asdfghasdfgh.de, 2 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain asdfghasdfgh.de, 2 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.asdfghasdfgh.de, 2 ip addresses.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.asdfghasdfgh.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:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 2 Queries complete, 2 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.asdfghasdfgh.de (2a03:6000:93f1:620::30, 46.23.93.30), ns2.asdfghasdfgh.de (217.197.83.164, 2a0a:4580:102e::1), ns3.asdfghasdfgh.de (130.0.206.23, 2a01:7a00:adab:206::e)
AGood (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.asdfghasdfgh.de, ns2.asdfghasdfgh.de, ns3.asdfghasdfgh.de, 3 Name Servers included in Delegation: ns1.asdfghasdfgh.de, ns2.asdfghasdfgh.de, ns3.asdfghasdfgh.de, 3 Name Servers included in 2 Zone definitions: ns1.asdfghasdfgh.de, ns2.asdfghasdfgh.de, ns3.asdfghasdfgh.de, 1 Name Servers listed in SOA.Primary: ns1.asdfghasdfgh.de.
AGood: Only one SOA.Primary Name Server found.: ns1.asdfghasdfgh.de.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.asdfghasdfgh.de.
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: de
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: asdfghasdfgh.de
AGood: Name servers with different Country locations found: 3 Name Servers, 3 Countries: DE, NL, SE
AInfo: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 130., 217., 46., 3 different subnets (first two Bytes): 130.0., 217.197., 46.23., 3 different subnets (first three Bytes): 130.0.206., 217.197.83., 46.23.93.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 3 different subnets (first block): 2a01:, 2a03:, 2a0a:, 3 different subnets (first two blocks): 2a01:7a00:, 2a03:6000:, 2a0a:4580:, 3 different subnets (first three blocks): 2a01:7a00:adab:, 2a03:6000:93f1:, 2a0a:4580:102e:, 3 different subnets (first four blocks): 2a01:7a00:adab:0206:, 2a03:6000:93f1:0620:, 2a0a:4580:102e:0000:
AExcellent: Every Name Server IPv6-address starts with an unique Hex-block
Nameserver doesn't pass all EDNS-Checks: ns1.asdfghasdfgh.de: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns1.asdfghasdfgh.de / 46.23.93.30: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns1.asdfghasdfgh.de / 2a03:6000:93f1:620::30: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
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

http://asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.23.93.30
-102

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:6000:93f1:620::30
-102

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 46.23.93.30
-102

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.asdfghasdfgh.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a03:6000:93f1:620::30
-102

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 142284 milliseconds, 142.284 seconds

 

8. Connections

No connection informations found. Perhaps only http - connections.

 

9. Certificates

No certificate informations found. Perhaps only http - connections.

 

10. Last Certificates - Certificate Transparency Log Check

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

Issuerlast 7 daysactivenum Certs
CN=R10, O=Let's Encrypt, C=US
0
14
14
CN=R11, O=Let's Encrypt, C=US
0
10
10

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
9178912299
leaf cert		CN=R11, O=Let's Encrypt, C=US
2025-01-10 12:31:57
2025-04-10 12:31:56
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, rss.asdfghasdfgh.de, update.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 8 entries


9178885743
leaf cert		CN=R10, O=Let's Encrypt, C=US
2025-01-10 12:27:33
2025-04-10 12:27:32
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, update.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 9 entries


9178165781
leaf cert		CN=R10, O=Let's Encrypt, C=US
2025-01-10 10:33:27
2025-04-10 10:33:26
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, update.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 9 entries


9113688488
leaf cert		CN=R10, O=Let's Encrypt, C=US
2025-01-03 08:47:07
2025-04-03 08:47:06
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 8 entries


9106304770
leaf cert		CN=R10, O=Let's Encrypt, C=US
2025-01-02 12:48:24
2025-04-02 12:48:23
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 8 entries


9106303221
leaf cert		CN=R10, O=Let's Encrypt, C=US
2025-01-02 12:47:53
2025-04-02 12:47:52
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 8 entries


9105610269
leaf cert		CN=R10, O=Let's Encrypt, C=US
2025-01-02 10:54:52
2025-04-02 10:54:51
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 8 entries


9101235823
leaf cert		CN=R11, O=Let's Encrypt, C=US
2025-01-01 23:31:44
2025-04-01 23:31:43
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 8 entries


9099504189
leaf cert		CN=R10, O=Let's Encrypt, C=US
2025-01-01 18:01:38
2025-04-01 18:01:37
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, ns1.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 8 entries


9088228689
leaf cert		CN=R10, O=Let's Encrypt, C=US
2024-12-31 09:55:15
2025-03-31 09:55:14
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 7 entries


9076175717
leaf cert		CN=R10, O=Let's Encrypt, C=US
2024-12-30 00:40:20
2025-03-30 00:40:19
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, reddit.asdfghasdfgh.de, rss.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 7 entries


8986674428
leaf cert		CN=R11, O=Let's Encrypt, C=US
2024-12-20 06:29:26
2025-03-20 06:29:25
asdfghasdfgh.de, bgp.asdfghasdfgh.de, honk.asdfghasdfgh.de, rss.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 7 entries


8786711053
leaf cert		CN=R10, O=Let's Encrypt, C=US
2024-11-28 23:10:35
2025-02-26 23:10:34
asdfghasdfgh.de, honk.asdfghasdfgh.de, rss.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 6 entries


8768454667
leaf cert		CN=R11, O=Let's Encrypt, C=US
2024-11-27 00:47:13
2025-02-25 00:47:12
asdfghasdfgh.de, honk.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 5 entries


8768472455
leaf cert		CN=R11, O=Let's Encrypt, C=US
2024-11-27 00:46:52
2025-02-25 00:46:51
asdfghasdfgh.de, honk.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 5 entries


8713378380
leaf cert		CN=R10, O=Let's Encrypt, C=US
2024-11-20 23:31:45
2025-02-18 23:31:44
asdfghasdfgh.de, honk.asdfghasdfgh.de, pub.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 6 entries


8709891524
leaf cert		CN=R10, O=Let's Encrypt, C=US
2024-11-20 14:29:12
2025-02-18 14:29:11
asdfghasdfgh.de, honk.asdfghasdfgh.de, proxy.asdfghasdfgh.de, pub.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 7 entries


8714774017
leaf cert		CN=R10, O=Let's Encrypt, C=US
2024-11-20 14:28:35
2025-02-18 14:28:34
asdfghasdfgh.de, honk.asdfghasdfgh.de, proxy.asdfghasdfgh.de, pub.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de - 6 entries


8709607986
leaf cert		CN=R10, O=Let's Encrypt, C=US
2024-11-20 13:14:15
2025-02-18 13:14:14
asdfghasdfgh.de, honk.asdfghasdfgh.de, proxy.asdfghasdfgh.de, pub.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 7 entries


8665617799
leaf cert		CN=R11, O=Let's Encrypt, C=US
2024-11-15 10:01:14
2025-02-13 10:01:13
asdfghasdfgh.de, honk.asdfghasdfgh.de, proxy.asdfghasdfgh.de, pub.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 7 entries


8665616861
leaf cert		CN=R11, O=Let's Encrypt, C=US
2024-11-15 10:00:50
2025-02-13 10:00:49
asdfghasdfgh.de, honk.asdfghasdfgh.de, proxy.asdfghasdfgh.de, pub.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 7 entries


8599428679
leaf cert		CN=R11, O=Let's Encrypt, C=US
2024-11-07 01:45:17
2025-02-05 01:45:16
asdfghasdfgh.de, honk.asdfghasdfgh.de, proxy.asdfghasdfgh.de, pub.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, znc.asdfghasdfgh.de - 7 entries


8586583528
leaf cert		CN=R11, O=Let's Encrypt, C=US
2024-11-05 23:31:42
2025-02-03 23:31:41
asdfghasdfgh.de, conference.asdfghasdfgh.de, dav.asdfghasdfgh.de, gotweb.asdfghasdfgh.de, honk.asdfghasdfgh.de, matrix.asdfghasdfgh.de, proxy.asdfghasdfgh.de, pub.asdfghasdfgh.de, share.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, www.asdfghasdfgh.de, xmpp.asdfghasdfgh.de, znc.asdfghasdfgh.de - 13 entries


8494996325
leaf cert		CN=R11, O=Let's Encrypt, C=US
2024-10-25 16:44:42
2025-01-23 16:44:41
asdfghasdfgh.de, conference.asdfghasdfgh.de, dav.asdfghasdfgh.de, gotweb.asdfghasdfgh.de, honk.asdfghasdfgh.de, ldap.asdfghasdfgh.de, matrix.asdfghasdfgh.de, proxy.asdfghasdfgh.de, pub.asdfghasdfgh.de, rss.asdfghasdfgh.de, searx.asdfghasdfgh.de, share.asdfghasdfgh.de, t1ns.asdfghasdfgh.de, vm20.asdfghasdfgh.de, wiki.asdfghasdfgh.de, www.asdfghasdfgh.de, xmpp.asdfghasdfgh.de, znc.asdfghasdfgh.de - 18 entries


 

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

No CRT - CT-Log entries found

 

11. Html-Content - Entries

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

 

12. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

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

 

QNr.DomainTypeNS used
1
de
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
2
ns1.asdfghasdfgh.de: 2a03:6000:93f1:620::30, 46.23.93.30
NS
a.nic.de (2001:678:2::53)

Answer: ns2.asdfghasdfgh.de
217.197.83.164, 2a0a:4580:102e::1

Answer: ns3.asdfghasdfgh.de
130.0.206.23, 2a01:7a00:adab:206::e

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.asdfghasdfgh.de
0

no CAA entry found
2
0
asdfghasdfgh.de
0

no CAA entry found
2
0
de
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
asdfghasdfgh.de
apple-domain=samHrkcVPZ1rTUqQ
ok
1
0
asdfghasdfgh.de
v=spf1 include:icloud.com ~all
ok
1
0
www.asdfghasdfgh.de

ok
1
0
_acme-challenge.asdfghasdfgh.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.asdfghasdfgh.de

Name Error - The domain name does not exist
1
0
_acme-challenge.asdfghasdfgh.de.asdfghasdfgh.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.asdfghasdfgh.de.asdfghasdfgh.de

Name Error - The domain name does not exist
1
0
_acme-challenge.www.asdfghasdfgh.de.www.asdfghasdfgh.de

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

asdfghasdfgh.de
10
mx02.mail.icloud.com
02ok

CNAME


-50ok
MX

asdfghasdfgh.de
10
mx01.mail.icloud.com
02ok

CNAME


-50ok
SPF
TXT
asdfghasdfgh.de

v=spf1 include:icloud.com ~all
ok

TXT
icloud.com

v=spf1 ip4:17.41.0.0/16 ip4:17.58.0.0/16 ip4:17.142.0.0/15 ip4:17.57.155.0/24 ip4:17.57.156.0/24 ip4:10.162.0.0/16 ip4:144.178.36.0/24 ip4:144.178.38.0/24 ip4:112.19.199.64/29 ip4:112.19.242.64/29 ip4:222.73.195.64/29 ip4:157.255.1.64/29 ip4:106.39.212.64/29 ip4:123.126.78.64/29 ip4:183.240.219.64/29 ip4:39.156.163.64/29 ip4:17.143.234.140/30 ip4:57.103.64.0/18 ~all
256Private ip address found

TXT
icloud.com

ip4:10.162.0.0
256Private ip address found
_dmarc
TXT
_dmarc.asdfghasdfgh.de

v=DMARC1; p=quarantine; rua=mailto:mk+dmarc-def394d3@asdfghasdfgh.de; ruf=mailto:mk+dmarc-def394d3@asdfghasdfgh.de; fo=1; pct=100; adkim=s; aspf=s
ok
SSHFP

asdfghasdfgh.de

3B0148C7B7ED4CD7548DD0E5A3F46853AFE4380E
Algorithmus RSA (1), FP-Type SHA-1 (1)		06ok
SSHFP

asdfghasdfgh.de

6BE5FE8D4B0D802618E82A7C601C0B6AEA55A18717EB03FA3317E90B0AE47964
Algorithmus RSA (1), FP-Type SHA-256 (2)		06ok
SSHFP

asdfghasdfgh.de

BB7DF13D694EB5B04DEF8DC6F2BE77A736540C36
Algorithmus ECDSA (3), FP-Type SHA-1 (1)		06ok
SSHFP

asdfghasdfgh.de

4E7BBE1D30116BA64D37E3F27D10255B3A503BFCFEAFAB2E318169AC80D6542D
Algorithmus ECDSA (3), FP-Type SHA-256 (2)		06ok
SSHFP

asdfghasdfgh.de

4AA83343643DDBA43D6B6A3F0D8DE6733CD07970
Algorithmus Ed25519 (4), FP-Type SHA-1 (1)		06ok
SSHFP

asdfghasdfgh.de

58C64F1A51241AAE3E76A33553BBE3669D3D46A026E9DC8EAEFA9F08413F99B2
Algorithmus Ed25519 (4), FP-Type SHA-256 (2)		06ok

				 
			

				 
			
17. Cipher Suites
No results 

				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=fc1b4d39-a064-4dfd-8423-1a2cd62b22eb

				 
			


Last Result: https://check-your-website.server-daten.de/?q=asdfghasdfgh.de - 2025-01-14 10:40:33

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

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

				 
			
QR-Code of this page - https://check-your-website.server-daten.de/?d=asdfghasdfgh.de

				 
			

				 
			



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