haw-landshut.de

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

deneb.dfn.de, dns1.fh-landshut.de, dns2.fh-landshut.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
deneb.dfn.de, dns1.fh-landshut.de, dns2.fh-landshut.de
NS in the zone
deneb.dfn.de, dns1.fh-landshut.de, dns2.fh-landshut.de
NameserverAddressesNetwork (AS)Glue
deneb.dfn.de192.76.176.9 2001:638:800:1::9AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE-
dns1.fh-landshut.de193.175.141.54AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE193.175.141.54
dns2.fh-landshut.de193.175.141.56AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE193.175.141.56

Checks

  • ✓ 3 nameservers #6
    Delegated to deneb.dfn.de, dns1.fh-landshut.de, dns2.fh-landshut.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 2 IPv4 /24s and 1 IPv6 /48.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: dns1.fh-landshut.de, dns2.fh-landshut.de.
    #13

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
deneb.dfn.de 192.76.176.9NOERROR, 14 ms, authoritativenoyes / yesrefused0
deneb.dfn.de 2001:638:800:1::9NOERROR, 14 ms, authoritativenoyes / yesrefused0
dns1.fh-landshut.de 193.175.141.54NOERROR, 13 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu
dns2.fh-landshut.de 193.175.141.56NOERROR, 13 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu

Checks

  • ✓ All respond #14
    All 4 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: dns1.fh-landshut.de: "9.18.39-0ubuntu0.22.04.7-Ubuntu"; dns2.fh-landshut.de: "9.18.39-0ubuntu0.22.04.7-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

pass

serial 2017119167 · primary dns1.fh-landshut.de

Found

Primary (MNAME)
dns1.fh-landshut.de
Contact (RNAME)
it-infrastruktur.haw-landshut.de
Serial
2017119167
Refresh / retry
21600 s / 1800 s
Expire
604800 s
Negative TTL
38400 s

Serial per nameserver

NameserverSerial
deneb.dfn.de (192.76.176.9)2017119167
deneb.dfn.de (2001:638:800:1::9)2017119167
dns1.fh-landshut.de (193.175.141.54)2017119167
dns2.fh-landshut.de (193.175.141.56)2017119167

Checks

  • ✓ Serial 2017119167 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 30m, expire 7d, negative TTL 640m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.fh-landshut.de is one of the listed nameservers.
  • ✓ Contact it-infrastruktur@haw-landshut.de #25
    The SOA RNAME it-infrastruktur.haw-landshut.de means it-infrastruktur@haw-landshut.de.
  • ✓ Timestamp serial #26
    The serial 2017119167 is a Unix timestamp (2033-12-02 06:52 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

8 records at the apex

Found

Read from
192.76.176.9:53
TypeValueTTL
SOAdns1.fh-landshut.de. it-infrastruktur.haw-landshut.de. 2017119167 21600 1800 604800 3840036180
NSdeneb.dfn.de.38400
NSdns2.fh-landshut.de.38400
NSdns1.fh-landshut.de.38400
A94.16.111.123600
MX10 postrelay1.lrz.de.300
MX10 postrelay2.lrz.de.300
TXT"v=spf1 a:mx01.haw-landshut.de a:mx02.haw-landshut.de a:mx01-22.haw-landshut.de a:mx02-22.haw-landshut.de a:bvbvxmail.bib-bvb.de include:_spf.mail.lrz.de ~all"300

Checks

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