netsplit.de

Checked 21 October 2026, 23:31 UTC · via 8.8.8.8
!Passed with warnings
19 passed 4 warnings 0 failed 6 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

gate.next-provider.net, ns.next-provider.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
gate.next-provider.net, ns.next-provider.net
NS in the zone
gate.next-provider.net, ns.next-provider.net
NameserverAddressesNetwork (AS)Glue
gate.next-provider.net5.9.84.182AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns.next-provider.net136.243.105.57AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: gate.next-provider.net, ns.next-provider.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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online 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 .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
  • !
    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
gate.next-provider.net 5.9.84.182NOERROR, 5 ms, authoritativenoyes / norefused-
ns.next-provider.net 136.243.105.57NOERROR, 6 ms, authoritativenoyes / norefused-

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.
  • ✓ 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.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: gate.next-provider.net (5.9.84.182), ns.next-provider.net (136.243.105.57).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 1791508993 · primary ns.next-provider.net

Found

Primary (MNAME)
ns.next-provider.net
Contact (RNAME)
hostmaster.next-provider.net
Serial
1791508993
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
gate.next-provider.net (5.9.84.182)1791508993
ns.next-provider.net (136.243.105.57)1792625280

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 1791508993 on gate.next-provider.net (5.9.84.182); 1792625280 on ns.next-provider.net (136.243.105.57). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.next-provider.net is one of the listed nameservers.
  • ✓ Contact hostmaster@next-provider.net #25
    The SOA RNAME hostmaster.next-provider.net means hostmaster@next-provider.net.
  • ✓ Timestamp serial #26
    The serial 1791508993 is a Unix timestamp (2026-10-09 01:23 UTC).

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
5.9.84.182:53
TypeValueTTL
SOAns.next-provider.net. hostmaster.next-provider.net. 1791508993 14400 3600 604800 8640086400
NSns.next-provider.net.259200
NSgate.next-provider.net.259200
A85.25.9.12686400
MX10 netsplit.de.86400
TXT"google-site-verification=J0RcIutuqJ5MxOX-W4AuVp5ETCYHGU4uXxbcYhFw7yA"3600
TXT"v=spf1 +a +mx +ip4:85.25.10.40 include:_spf.google.com -all"3600

Checks

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