zugspitze.de

Checked 22 October 2026, 01:20 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

ns01.infra.net, ns02.infra.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns01.infra.net, ns02.infra.net
NS in the zone
ns01.infra.net, ns02.infra.net
NameserverAddressesNetwork (AS)Glue
ns01.infra.net195.242.206.3AS12830 INFRA-MAIN-AS - InfraNet AG, DE-
ns02.infra.net195.242.206.2AS12830 INFRA-MAIN-AS - InfraNet AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.infra.net, ns02.infra.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 one network
    all IPv4 addresses are in 195.242.206.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 (AS12830 (INFRA-MAIN-AS - InfraNet AG, 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
ns01.infra.net 195.242.206.3NOERROR, 15 ms, authoritativenoyes / yesrefused21.3.1-teletubbies
ns02.infra.net 195.242.206.2NOERROR, 16 ms, authoritativenoyes / yesrefused21.3.1-teletubbies

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: ns01.infra.net: "21.3.1-teletubbies"; ns02.infra.net: "21.3.1-teletubbies". 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

pass

serial 2026092101 · primary ns01.infra.net

Found

Primary (MNAME)
ns01.infra.net
Contact (RNAME)
hostmaster.infra.net
Serial
2026092101
Refresh / retry
10000 s / 2500 s
Expire
864000 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns01.infra.net (195.242.206.3)2026092101
ns02.infra.net (195.242.206.2)2026092101

Checks

  • ✓ Serial 2026092101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 41m40s, expire 10d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.infra.net is one of the listed nameservers.
  • ✓ Contact hostmaster@infra.net #25
    The SOA RNAME hostmaster.infra.net means hostmaster@infra.net.
  • ✓ Date-based serial #26
    The serial 2026092101 follows the YYYYMMDDnn convention (2026-09-21).

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

12 records at the apex

Found

Read from
195.242.206.3:53
TypeValueTTL
SOAns01.infra.net. hostmaster.infra.net. 2026092101 10000 2500 864000 36001800
NSns02.infra.net.1800
NSns01.infra.net.1800
A195.242.206.1971800
MX10 mx01.hornetsecurity.com.1800
MX20 mx02.hornetsecurity.com.1800
MX30 mx03.hornetsecurity.com.1800
MX40 mx04.hornetsecurity.com.1800
TXT"v=spf1 include:spf.protection.outlook.com include:spf-de.emailsignatures365.com include:spf.ikomm.de include:spf.hornetsecurity.com ip4:195.242.206.192/29 include:_spf.skiperformance.com include:_spf.xurrent.qa include:_spf.xurrent.com -all"1800
TXT"MS=9A3E05CB83EE137427921F50E62E56426C513DC3"1800
TXT"swisssign-check=oV8LzeQ69d011MLt6tv972QBAUc"1800
TXT"langdock-verify=EpksxfbkMHfn6ChMBqeOAH0A9ibagGR4iKDJdlhEziQ"1800

Checks

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