musin.de

Checked 21 October 2026, 23:31 UTC · via 8.8.8.8
✗Problems found
15 passed 5 warnings 2 failed 7 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

ns.musin.de, ns2.musin.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.musin.de, ns2.musin.de
NS in the zone
ns.musin.de, ns2.musin.de, ns3.musin.de
NameserverAddressesNetwork (AS)Glue
ns.musin.de194.113.40.45AS203989 LHM-PAED - Landeshauptstadt Muenchen, it@M, DE194.113.40.45
ns2.musin.de194.113.40.54AS203989 LHM-PAED - Landeshauptstadt Muenchen, it@M, DE194.113.40.54
ns3.musin.de (zone only)194.113.40.43AS203989 LHM-PAED - Landeshauptstadt Muenchen, it@M, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.musin.de, ns2.musin.de.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.musin.de. ns.musin.de, ns2.musin.de report NS ns.musin.de ns2.musin.de ns3.musin.de.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns.musin.de, ns2.musin.de.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 194.113.40.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 (AS203989 (LHM-PAED - Landeshauptstadt Muenchen, it@M, DE): 3 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 .de
    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

fail

2 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.musin.de 194.113.40.45NOERROR, 10 ms, authoritativenoyes / yesrefusednone
ns2.musin.de 194.113.40.54NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns3.musin.de 194.113.40.43SERVFAIL, 10 ms, NOT authoritativenono / yesrefused-

Checks

  • ✓ All respond #14
    All 3 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns3.musin.de (194.113.40.43): SERVFAIL, authoritative=false.
    #15
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns.musin.de: "none".
    #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: ns3.musin.de (194.113.40.43): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026102100 · primary ns.musin.de

Found

Primary (MNAME)
ns.musin.de
Contact (RNAME)
root.musin.de
Serial
2026102100
Refresh / retry
1800 s / 1800 s
Expire
3600000 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns.musin.de (194.113.40.45)2026102100
ns2.musin.de (194.113.40.54)2026102100

Checks

  • ✓ Serial 2026102100 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 30m should be shorter than refresh 30m. Current values: refresh 30m, retry 30m, expire 1000h, negative TTL 10m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.musin.de is one of the listed nameservers.
  • ✓ Contact root@musin.de #25
    The SOA RNAME root.musin.de means root@musin.de.
  • ✓ Date-based serial #26
    The serial 2026102100 follows the YYYYMMDDnn convention (2026-10-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

11 records at the apex

Found

Read from
194.113.40.45:53
TypeValueTTL
SOAns.musin.de. root.musin.de. 2026102100 1800 1800 3600000 600600
NSns3.musin.de.600
NSns2.musin.de.600
NSns.musin.de.600
MX10 mail.musin.de.600
MX5 smtpmx.m-bildung.de.600
TXT"apple-domain-verification=gAW8zWmbgIPvO0Z8"600
TXT"_telesec-domain-validation=271153_2019-05-13_6fjMp30kwVgk6ocjxeBBk5SdDxrOfiXrUKHZpAxywKPZHUcqe6"600
TXT"MS=ms80736062"600
TXT"v=spf1 mx ?all"600
TXT"google-site-verification=nYowlmPqH90s5ZRu1bReyefLU3RZaABisNeOXz-GxMU"600

Checks

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