berchtesgaden.de

Checked 21 October 2026, 21:37 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

ns.space.net, ns3.dns.space.net, ns4.dns.space.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.space.net, ns3.dns.space.net, ns4.dns.space.net
NS in the zone
ns.space.net, ns3.dns.space.net, ns4.dns.space.net
NameserverAddressesNetwork (AS)Glue
ns.space.net195.30.0.10 2001:608:0:a::1AS5539 SPACENET - SpaceNet AG, DE AS5539 SPACENET - SpaceNet AG, DE-
ns3.dns.space.net193.149.44.49 2001:608:0:f0f::fAS5539 SPACENET - SpaceNet AG, DE AS5539 SPACENET - SpaceNet AG, DE-
ns4.dns.space.net194.97.129.1 2001:608:0:b::1AS5539 SPACENET - SpaceNet AG, DE AS5539 SPACENET - SpaceNet AG, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns.space.net, ns3.dns.space.net, ns4.dns.space.net.
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:608::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS5539 (SPACENET - SpaceNet AG, DE): 6 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.space.net 195.30.0.10NOERROR, 11 ms, authoritativenoyes / yesrefusedKnot DNS 3.6.0
ns.space.net 2001:608:0:a::1NOERROR, 12 ms, authoritativenoyes / yesrefusedKnot DNS 3.6.0
ns3.dns.space.net 193.149.44.49NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns3.dns.space.net 2001:608:0:f0f::fNOERROR, 3 ms, authoritativenoyes / yesrefused-
ns4.dns.space.net 194.97.129.1NOERROR, 12 ms, authoritativenoyes / yesrefused9.20.24
ns4.dns.space.net 2001:608:0:b::1NOERROR, 11 ms, authoritativenoyes / yesrefused9.20.24

Checks

  • ✓ All respond #14
    All 6 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: ns.space.net: "Knot DNS 3.6.0"; ns4.dns.space.net: "9.20.24". 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 1785938066 · primary ns.space.net

Found

Primary (MNAME)
ns.space.net
Contact (RNAME)
hostmaster.space.net
Serial
1785938066
Refresh / retry
28800 s / 3600 s
Expire
864000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns.space.net (195.30.0.10)1785938066
ns.space.net (2001:608:0:a::1)1785938066
ns3.dns.space.net (193.149.44.49)1785938066
ns3.dns.space.net (2001:608:0:f0f::f)1785938066
ns4.dns.space.net (194.97.129.1)1785938066
ns4.dns.space.net (2001:608:0:b::1)1785938066

Checks

  • ✓ Serial 1785938066 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 1h, expire 10d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.space.net is one of the listed nameservers.
  • ✓ Contact hostmaster@space.net #25
    The SOA RNAME hostmaster.space.net means hostmaster@space.net.
  • ✓ Timestamp serial #26
    The serial 1785938066 is a Unix timestamp (2026-08-05 13:54 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

11 records at the apex

Found

Read from
195.30.0.10:53
TypeValueTTL
SOAns.space.net. hostmaster.space.net. 1785938066 28800 3600 864000 864003600
NSns.space.net.3600
NSns3.dns.space.net.3600
NSns4.dns.space.net.3600
A49.12.23.1853600
AAAA2a01:4f8:c011:469::13600
MX100 gatekeeper.space.net.3600
MX100 gatekeeper.spacenet.de.3600
TXT"MS=ms62619854"3600
TXT"google-site-verification=LSi1EM6OeWrK6MSM8RYnTGecy9sV0arKMlSxkZqAzNg"3600
TXT"v=spf1 mx a:spacemail.berchtesgaden.de a:wan1.berchtesgaden.de include:spf.mailjet.com ~all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, 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.
  • ✓ 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