dimdi.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 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

warn

ns02.versatel.de, ns1.dimdi.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns02.versatel.de, ns1.dimdi.de
NS in the zone
ns02.versatel.de, ns1.dimdi.de
NameserverAddressesNetwork (AS)Glue
ns02.versatel.de212.7.128.165AS8881 VERSATEL - 1&1 Versatel GmbH, DE212.7.128.165
ns1.dimdi.de194.153.219.2AS6733 BfArM - Bundesinstitut fuer Arzneimittel und Medizinprodukte (BfArM), DE194.153.219.2

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns02.versatel.de, ns1.dimdi.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.dimdi.de.
  • ✓ 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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS6733 (BfArM - Bundesinstitut fuer Arzneimittel und Medizinprodukte (BfArM), DE): 1 address; AS8881 (VERSATEL - 1&1 Versatel GmbH, DE): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns02.versatel.de 212.7.128.165NOERROR, 17 ms, authoritativenoyes / yesrefusedNo version info available (refused).
ns1.dimdi.de 194.153.219.2NOERROR, 8 ms, authoritativenoyes / yesrefused9.18.49-1~deb12u2-Debian

Checks

  • ✓ All respond #14
    All 2 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.dimdi.de: "9.18.49-1~deb12u2-Debian". Hide or replace the version string.
    #17
  • ✓ 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 2026093000 · primary ns1.dimdi.de

Found

Primary (MNAME)
ns1.dimdi.de
Contact (RNAME)
hostmaster.bfarm.de
Serial
2026093000
Refresh / retry
10800 s / 3600 s
Expire
1814400 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns02.versatel.de (212.7.128.165)2026093000
ns1.dimdi.de (194.153.219.2)2026093000

Checks

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

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

8 records at the apex

Found

Read from
212.7.128.165:53
TypeValueTTL
SOAns1.dimdi.de. hostmaster.bfarm.de. 2026093000 10800 3600 1814400 8640010800
NSns02.versatel.de.10800
NSns1.dimdi.de.10800
A194.153.219.6610800
MX20 mx-d2.bfarm.de.600
MX10 mx-d1.bfarm.de.600
TXT"HARICA-qRE5Lo6V7TUM0BvGQqr"10800
TXT"v=spf1 a a:srv01mailgw.dimdi.de a:srv02mailgw.dimdi.de a:srv03mailgw.dimdi.de a:srv04mailgw.dimdi.de -all"10800

Checks

  • ✓ TTLs within range #32
    TTLs: A 3h, MX 10m, NS 3h. The NS TTL at the parent is 1d and in the zone 3h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35