delius-klasing.de

Checked 21 October 2026, 22:12 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 0 failed 5 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
ICANN policies apply
no

Checks

  • i
    .de is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .de is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

info

ns1.adns2.de, ns2.adns2.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.adns2.de, ns2.adns2.de
NS in the zone
ns1.adns2.de, ns2.adns2.de
NameserverAddressesNetwork (AS)Glue
ns1.adns2.de217.31.82.10 2a00:15a8:1::d91f:520a:1AS29140 HOSTSERVER-AS - Hostserver GmbH, DE AS29140 HOSTSERVER-AS - Hostserver GmbH, DE217.31.82.10 2a00:15a8:1::d91f:520a:1
ns2.adns2.de62.116.145.206 2001:4178:2:1318::8a4f:53AS15456 INTERNETX-AS - InterNetX GmbH, DE AS15456 INTERNETX-AS - InterNetX GmbH, DE62.116.145.206 2001:4178:2:1318::8a4f:53

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.adns2.de, ns2.adns2.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15456 (INTERNETX-AS - InterNetX GmbH, DE): 2 addresses; AS29140 (HOSTSERVER-AS - Hostserver GmbH, DE): 2 addresses.
  • i
    All nameserver names under .de
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.adns2.de 217.31.82.10NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.adns2.de 2a00:15a8:1::d91f:520a:1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.adns2.de 62.116.145.206NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.adns2.de 2001:4178:2:1318::8a4f:53NOERROR, 10 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026091100 · primary ns1.adns2.de

Found

Primary (MNAME)
ns1.adns2.de
Contact (RNAME)
hostmaster.adns2.de
Serial
2026091100
Refresh / retry
39940 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.adns2.de (217.31.82.10)2026091100
ns1.adns2.de (2a00:15a8:1::d91f:520a:1)2026091100
ns2.adns2.de (62.116.145.206)2026091100
ns2.adns2.de (2001:4178:2:1318::8a4f:53)2026091100

Checks

  • ✓ Serial 2026091100 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 11h5m40s, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.adns2.de is one of the listed nameservers.
  • ✓ Contact hostmaster@adns2.de #25
    The SOA RNAME hostmaster.adns2.de means hostmaster@adns2.de.
  • ✓ Date-based serial #26
    The serial 2026091100 follows the YYYYMMDDnn convention (2026-09-11).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

info

21 records at the apex

Found

Read from
217.31.82.10:53
TypeValueTTL
SOAns1.adns2.de. hostmaster.adns2.de. 2026091100 39940 7200 604800 864001209600
NSns1.adns2.de.86400
NSns2.adns2.de.86400
A62.96.146.1973600
MX0 deliusklasing-de01e.mail.protection.outlook.com.3600
TXT"google-site-verification=QKpFpNDuDqPxF6_iZtY3Pt64_aJMrpmeZ0WtRqCHtc8"3600
TXT"vrNnrXHKp1VaTELyE38f8QzfG4vMMgoW42bCxsgf/cttH8YSx4Bb+oflSxpOfJhp6mBnvbWH8LJakoycRnMXXA=="3600
TXT"google-site-verification=s53EPo-z-b9m-xTFC8J6YOdbwrnh7HiIfIhqAC4-sck"3600
TXT"amazon-business-verification=1310b742487c6f2e2b6855e59f1a7a7df58ed4eae45c59eff2a95a726709d163"3600
TXT"v=spf1 include:spf.protection.outlook.com include:_spf.delius-klasing.de include:_spf.intan.net -all"3600
TXT"adobe-idp-site-verification=53c22b7c16b457f7833245b554a1e27c33c9f279b10c673b17835ad5b9aa2821"3600
TXT"2qsWJFdAw0rad5mQalBqs73TwXgoIjfv287r3UCDDmbMNPPFdKjYKz+wO5PGo1870J9yRjTsnzC+DLuoeuO2vA=="600
TXT"f5a0a02aa7cfeb76f85c11c6db64ada4b53e0f8464b6346a85e9b20603200f1"3600
TXT"google-site-verification=t87H1EqoRPh8V8CPfuZAIn3G4I0JqrZVOZVV1JLvO5o"3600
TXT"anthropic-domain-verification-25a2mx=KiXAvyYztLVOn0OHvAJ0UTDVG"3600
CAA0 issue "awstrust.com"3600
CAA0 issue "letsencrypt.org"3600
CAA0 issuewild "certum.pl"3600
CAA0 issue "sectigo.com"3600
CAA0 issue "certum.pl"3600
CAA0 issue "globalsign.com"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 1d.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: awstrust.com, letsencrypt.org, certum.pl, sectigo.com, globalsign.com.