hfm-weimar.de

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

warn

dns.htwm.de, dns1.uni-weimar.de, dns2.uni-weimar.de, tigger.scc.uni-weimar.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns.htwm.de, dns1.uni-weimar.de, dns2.uni-weimar.de, tigger.scc.uni-weimar.de
NS in the zone
dns.htwm.de, dns1.uni-weimar.de, dns2.uni-weimar.de, tigger.scc.uni-weimar.de
NameserverAddressesNetwork (AS)Glue
dns.htwm.de141.55.192.50AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE-
dns1.uni-weimar.de141.54.65.1AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE141.54.65.1
dns2.uni-weimar.de141.54.100.129AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE141.54.100.129
tigger.scc.uni-weimar.de141.54.1.3AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE141.54.1.3

Checks

  • ✓ 4 nameservers #6
    Delegated to dns.htwm.de, dns1.uni-weimar.de, dns2.uni-weimar.de, tigger.scc.uni-weimar.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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS680 (DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE): 4 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

3 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns.htwm.de 141.55.192.50REFUSED, 18 ms, NOT authoritativenono / yesrefused-
dns1.uni-weimar.de 141.54.65.1NOERROR, 13 ms, authoritativenoyes / yesrefused-
dns2.uni-weimar.de 141.54.100.129NOERROR, 13 ms, authoritativenoyes / yesrefused-
tigger.scc.uni-weimar.de 141.54.1.3NOERROR, 13 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: dns.htwm.de (141.55.192.50): REFUSED, authoritative=false.
    #15
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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: dns.htwm.de (141.55.192.50): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026100700 · primary tigger.scc.uni-weimar.de

Found

Primary (MNAME)
tigger.scc.uni-weimar.de
Contact (RNAME)
hostmaster.uni-weimar.de
Serial
2026100700
Refresh / retry
10800 s / 3600 s
Expire
3600000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dns1.uni-weimar.de (141.54.65.1)2026100700
dns2.uni-weimar.de (141.54.100.129)2026100700
tigger.scc.uni-weimar.de (141.54.1.3)2026100700

Checks

  • ✓ Serial 2026100700 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 1000h, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver tigger.scc.uni-weimar.de is one of the listed nameservers.
  • ✓ Contact hostmaster@uni-weimar.de #25
    The SOA RNAME hostmaster.uni-weimar.de means hostmaster@uni-weimar.de.
  • ✓ Date-based serial #26
    The serial 2026100700 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

14 records at the apex

Found

Read from
141.54.65.1:53
TypeValueTTL
SOAtigger.scc.uni-weimar.de. hostmaster.uni-weimar.de. 2026100700 10800 3600 3600000 864007200
NSdns.htwm.de.7200
NSdns1.uni-weimar.de.7200
NStigger.scc.uni-weimar.de.7200
NSdns2.uni-weimar.de.7200
A141.54.193.57200
A141.54.193.47200
A141.54.193.187200
MX4 leia.uni-weimar.de.7200
MX3 luke.uni-weimar.de.7200
TXT"ZOOM_verify_m1HiL1uCbyTWWi6i05tCwP"3600
TXT"MS=ms83331002"3600
TXT"cisco-ci-domain-verification=381d19d4a152b414d6e8dd890af1a1d2d1614444ab06e4f634bd5db86c2ac676"3600
TXT"v=spf1 ip4:141.54.1.0/24 ip4:116.203.110.13 ip4:159.69.3.23 include:tu-ilmenau.de include:gbv.de -all"3600

Checks

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