fh-wedel.de

ns4.fh-wedel.de, nsnext.fh-wedel.de

Found

Parent zone

de

Delegation from

a.nic.de (194.0.0.53)

NS at the parent

ns4.fh-wedel.de, nsnext.fh-wedel.de

NS in the zone

ns4.fh-wedel.de, nsnext.fh-wedel.de

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns4.fh-wedel.de, nsnext.fh-wedel.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: ns4.fh-wedel.de, nsnext.fh-wedel.de.
• ✓ All names resolve #9

  Every nameserver name has an address and is not an alias.
• !

  Nameservers in one network

  all IPv4 addresses are in 213.209.120.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).

  #10
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS15943 (WTNET-AS - wilhelm.tel GmbH, DE): 2 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

  #11
• 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

2 of 2 addresses answer authoritatively

Found

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: nsnext.fh-wedel.de: "9.10.3-P4-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.

serial 2026102001 · primary nsnext.fh-wedel.de

Found

Primary (MNAME)

nsnext.fh-wedel.de

Contact (RNAME)

root.nsnext.fh-wedel.de

Serial

2026102001

Refresh / retry

900 s / 600 s

Expire

1209600 s

Negative TTL

1800 s

Serial per nameserver

Checks

• !

  Serials differ

  The nameservers serve different versions of the zone: 202610101 on nsnext.fh-wedel.de (213.209.120.222); 2026102001 on ns4.fh-wedel.de (213.209.120.130). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

  #22
• !

  Unusual SOA timers

  refresh 15m is outside 20m–1d. Current values: refresh 15m, retry 10m, expire 14d, negative TTL 30m.

  #23
• ✓ Primary is a public nameserver #24

  The primary nameserver nsnext.fh-wedel.de is one of the listed nameservers.
• ✓ Contact root@nsnext.fh-wedel.de #25

  The SOA RNAME root.nsnext.fh-wedel.de means root@nsnext.fh-wedel.de.
• ✓ Date-based serial #26

  The serial 2026102001 follows the YYYYMMDDnn convention (2026-10-20).

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