die-linke.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
✗Problems found
20 passed 2 warnings 2 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

ns1.routing.net, ns2.routing.net, ns3.routing.net, nsh.ipn.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.routing.net, ns2.routing.net, ns3.routing.net, nsh.ipn.de
NS in the zone
ns1.routing.net, ns2.routing.net, ns3.routing.net, nsh.ipn.de
NameserverAddressesNetwork (AS)Glue
ns1.routing.net134.0.30.178 2a03:2900:3:1::2AS48823 AS48823 - Hosting.de GmbH, DE AS48823 AS48823 - Hosting.de GmbH, DE-
ns2.routing.net194.50.113.2 2001:4d8f:2::2AS41637 ROUTING-ANYCAST - Hosting.de GmbH, DE AS41637 ROUTING-ANYCAST - Hosting.de GmbH, DE-
ns3.routing.net194.126.196.2 2a03:2902:3:1::2AS31400 ACCELERATED-IT - firstcolo GmbH, DE AS31400 ACCELERATED-IT - firstcolo GmbH, DE-
nsh.ipn.de157.90.122.239AS24940 HETZNER-AS - Hetzner Online GmbH, DE157.90.122.239

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.routing.net, ns2.routing.net, ns3.routing.net, nsh.ipn.de.
  • ✓ 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 4 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address; AS31400 (ACCELERATED-IT - firstcolo GmbH, DE): 2 addresses; AS41637 (ROUTING-ANYCAST - Hosting.de GmbH, DE): 2 addresses; AS48823 (AS48823 - Hosting.de GmbH, DE): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .de, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: nsh.ipn.de.
    #13

Nameservers

fail

1 of 7 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.routing.net 134.0.30.178REFUSED, 8 ms, NOT authoritativenono / yesrefused-
ns1.routing.net 2a03:2900:3:1::2REFUSED, 9 ms, NOT authoritativenono / yesrefused-
ns2.routing.net 194.50.113.2REFUSED, 9 ms, NOT authoritativenono / yesrefused-
ns2.routing.net 2001:4d8f:2::2REFUSED, 9 ms, NOT authoritativenono / yesrefused-
ns3.routing.net 194.126.196.2REFUSED, 4 ms, NOT authoritativenono / yesrefused-
ns3.routing.net 2a03:2902:3:1::2REFUSED, 4 ms, NOT authoritativenono / yesrefused-
nsh.ipn.de 157.90.122.239NOERROR, 2 ms, authoritativenoyes / yesrefused9.16.1-Ubuntu

Checks

  • ✓ All respond #14
    All 7 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns1.routing.net (134.0.30.178): REFUSED, authoritative=false; ns1.routing.net (2a03:2900:3:1::2): REFUSED, authoritative=false; ns2.routing.net (194.50.113.2): REFUSED, authoritative=false; ns2.routing.net (2001:4d8f:2::2): REFUSED, authoritative=false; ns3.routing.net (194.126.196.2): REFUSED, authoritative=false; ns3.routing.net (2a03:2902:3:1::2): REFUSED, authoritative=false.
    #15
  • ✓ 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: nsh.ipn.de: "9.16.1-Ubuntu". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.routing.net (134.0.30.178): ; ns1.routing.net (2a03:2900:3:1::2): ; ns2.routing.net (194.50.113.2): ; ns2.routing.net (2001:4d8f:2::2): ; ns3.routing.net (194.126.196.2): ; ns3.routing.net (2a03:2902:3:1::2): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 2026100702 · primary ns.ipn.de

Found

Primary (MNAME)
ns.ipn.de
Contact (RNAME)
support.ipn-b.de
Serial
2026100702
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
43200 s

Checks

  • ✓ Serial 2026100702 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 12h.
  • i
    Hidden master
    The primary nameserver ns.ipn.de is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact support@ipn-b.de #25
    The SOA RNAME support.ipn-b.de means support@ipn-b.de.
  • ✓ Date-based serial #26
    The serial 2026100702 follows the YYYYMMDDnn convention (2026-10-07).

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

15 records at the apex

Found

Read from
157.90.122.239:53
TypeValueTTL
SOAns.ipn.de. support.ipn-b.de. 2026100702 10800 3600 604800 432003600
NSns2.routing.net.3600
NSns1.routing.net.3600
NSnsh.ipn.de.3600
NSns3.routing.net.3600
A5.252.35.242300
MX10 mail.minuskel.de.3600
TXT"ZOOM_verify_m5iBWursFU1YP7A0XtSryJ"3600
TXT"v=spf1 include:_spf.minuskel.de a:webmail.die-linke.de ~all"3600
TXT"google-site-verification=7EgniBLnmOJqTNMc88qISfN9PFaGnPwYKh3dtwdxQmo"3600
TXT"ZOOM_verify_XaUlJDH3fQ3hh4YQ1mnxQx"3600
CAA0 issue "sectigo.com"3600
CAA0 issue "letsencrypt.org"3600
CAA0 issue "certum.pl"3600
CAA0 issuewild "certum.pl"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, 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.
  • 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: sectigo.com, letsencrypt.org, certum.pl.