die-gdi.de

Checked 21 October 2026, 22:14 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

dns.tops.net, ns2.tops.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns.tops.net, ns2.tops.net
NS in the zone
dns.tops.net, ns2.tops.net
NameserverAddressesNetwork (AS)Glue
dns.tops.net212.79.191.36 2a00:c940:9::2AS12581 TOPSNET - tops.net GmbH & Co. KG, DE AS12581 TOPSNET - tops.net GmbH & Co. KG, DE-
ns2.tops.net5.9.85.53 2a01:4f8:162:465::2AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns.tops.net, ns2.tops.net.
    #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: AS12581 (TOPSNET - tops.net GmbH & Co. KG, DE): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses.
  • i
    All nameserver names under .net
    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
dns.tops.net 212.79.191.36NOERROR, 8 ms, authoritativenoyes / yesrefused-
dns.tops.net 2a00:c940:9::2NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns2.tops.net 5.9.85.53NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.tops.net 2a01:4f8:162:465::2NOERROR, 3 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 2026090101 · primary dns.tops.net

Found

Primary (MNAME)
dns.tops.net
Contact (RNAME)
guardian.tops.net
Serial
2026090101
Refresh / retry
28800 s / 7200 s
Expire
1814400 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dns.tops.net (212.79.191.36)2026090101
dns.tops.net (2a00:c940:9::2)2026090101
ns2.tops.net (5.9.85.53)2026090101
ns2.tops.net (2a01:4f8:162:465::2)2026090101

Checks

  • ✓ Serial 2026090101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 21d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns.tops.net is one of the listed nameservers.
  • ✓ Contact guardian@tops.net #25
    The SOA RNAME guardian.tops.net means guardian@tops.net.
  • ✓ Date-based serial #26
    The serial 2026090101 follows the YYYYMMDDnn convention (2026-09-01).

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

7 records at the apex

Found

Read from
212.79.191.36:53
TypeValueTTL
SOAdns.tops.net. guardian.tops.net. 2026090101 28800 7200 1814400 86400600
NSns2.tops.net.3600
NSdns.tops.net.3600
A87.230.93.195600
MX10 idosresearch-de01b.mail.protection.outlook.com.3600
TXT"_52biv5m2xakrxbne8rejpwj54z8078v"600
TXT"v=spf1 a mx a:webmail.die-gdi.de a:mail.die-gdi.de ip4:212.79.189.58 ip4:212.79.163.147 ip4:212.79.187.57 include:spf.protection.outlook.com include:spf.nl2go.com ~all"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 1h, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; 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