schaubuehne.de

Checked 22 October 2026, 00:01 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 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

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

warn

7 of 7 addresses answer authoritatively

Found

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

Checks

  • ✓ All respond #14
    All 7 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: 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.
  • ✓ 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

info

serial 2025012701 · primary ns.ipn.de

Found

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

Serial per nameserver

NameserverSerial
ns1.routing.net (134.0.30.178)2025012701
ns1.routing.net (2a03:2900:3:1::2)2025012701
ns2.routing.net (194.50.113.2)2025012701
ns2.routing.net (2001:4d8f:2::2)2025012701
ns3.routing.net (194.126.196.2)2025012701
ns3.routing.net (2a03:2902:3:1::2)2025012701
nsh.ipn.de (157.90.122.239)2025012701

Checks

  • ✓ Serial 2025012701 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 2025012701 follows the YYYYMMDDnn convention (2025-01-27).

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
134.0.30.178:53
TypeValueTTL
SOAns.ipn.de. support.ipn-b.de. 2025012701 10800 3600 604800 4320086400
NSns3.routing.net.86400
NSns1.routing.net.86400
NSnsh.ipn.de.86400
NSns2.routing.net.86400
A193.96.188.221300
MX10 mail.schaubuehne.de.86400
TXT"v=spf1 mx a include:spf.nl2go.com include:spf.mandrillapp.com ip4:193.96.188.0/24 ip4:87.129.250.152/29 ip4:217.92.184.243 -all"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1d, NS 1d.
  • ✓ 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