zoo-hannover.de

Checked 22 October 2026, 01:20 UTC · via 8.8.8.8
!Passed with warnings
21 passed 1 warning 0 failed 7 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

ns.pop-hannover.de, ns2.pop-hannover.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.pop-hannover.de, ns2.pop-hannover.net
NS in the zone
ns.pop-hannover.de, ns2.pop-hannover.net
NameserverAddressesNetwork (AS)Glue
ns.pop-hannover.de193.98.1.200 2a00:e68::2AS15743 NETDE - net.de AG, DE AS15743 NETDE - net.de AG, DE193.98.1.200 2a00:e68::2
ns2.pop-hannover.net62.48.67.66 2a00:e68:0:2::6AS15743 NETDE - net.de AG, DE AS15743 NETDE - net.de AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.pop-hannover.de, ns2.pop-hannover.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a00:e68::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS15743 (NETDE - net.de AG, DE): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.pop-hannover.de 193.98.1.200NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns.pop-hannover.de 2a00:e68::2NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.pop-hannover.net 62.48.67.66NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.pop-hannover.net 2a00:e68:0:2::6NOERROR, 11 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 2026012200 · primary ns.pop-hannover.de

Found

Primary (MNAME)
ns.pop-hannover.de
Contact (RNAME)
hostmaster.net.de
Serial
2026012200
Refresh / retry
21600 s / 3600 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns.pop-hannover.de (193.98.1.200)2026012200
ns.pop-hannover.de (2a00:e68::2)2026012200
ns2.pop-hannover.net (62.48.67.66)2026012200
ns2.pop-hannover.net (2a00:e68:0:2::6)2026012200

Checks

  • ✓ Serial 2026012200 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.pop-hannover.de is one of the listed nameservers.
  • ✓ Contact hostmaster@net.de #25
    The SOA RNAME hostmaster.net.de means hostmaster@net.de.
  • ✓ Date-based serial #26
    The serial 2026012200 follows the YYYYMMDDnn convention (2026-01-22).

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
193.98.1.200:53
TypeValueTTL
SOAns.pop-hannover.de. hostmaster.net.de. 2026012200 21600 3600 604800 600600
NSns2.pop-hannover.net.600
NSns.pop-hannover.de.600
A157.90.249.41600
MX10 zoohannover-de0i.mail.protection.outlook.com.600
TXT"MS=ms74934395"600
TXT"v=spf1 include:spf.protection.outlook.com -all"600
TXT"hy6b4g1k8b3cpjn89hcywqb28nftp0fs"600

Checks

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