hfwu.de

Checked 21 October 2026, 22:50 UTC · via 8.8.8.8
!Passed with warnings
19 passed 2 warnings 0 failed 8 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

dns1.belwue.de, dns3.belwue.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
dns1.belwue.de, dns3.belwue.de
NS in the zone
dns1.belwue.de, dns3.belwue.de
NameserverAddressesNetwork (AS)Glue
dns1.belwue.de129.143.2.10 2001:7c0::53:10AS553 BELWUE - Universitaet Stuttgart, DE AS553 BELWUE - Universitaet Stuttgart, DE129.143.2.10 2001:7c0::53:10
dns3.belwue.de129.143.253.133 2001:7c0:0:253::133AS553 BELWUE - Universitaet Stuttgart, DE AS553 BELWUE - Universitaet Stuttgart, DE129.143.253.133 2001:7c0:0:253::133

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.belwue.de, dns3.belwue.de.
    #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.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:7c0::/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 (AS553 (BELWUE - Universitaet Stuttgart, 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.belwue.de 129.143.2.10NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)
dns1.belwue.de 2001:7c0::53:10NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)
dns3.belwue.de 129.143.253.133NOERROR, 16 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)
dns3.belwue.de 2001:7c0:0:253::133NOERROR, 7 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)

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.belwue.de: "PowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)"; dns3.belwue.de: "PowerDNS Authoritative Server 4.5.5 (built Dec 8 2022 18:24:18 by root@a309361b6303)". 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

info

serial 2026101602 · primary dns.hfwu.de

Found

Primary (MNAME)
dns.hfwu.de
Contact (RNAME)
hostmaster.hfwu.de
Serial
2026101602
Refresh / retry
21600 s / 1800 s
Expire
2419200 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
dns1.belwue.de (129.143.2.10)2026101602
dns1.belwue.de (2001:7c0::53:10)2026101602
dns3.belwue.de (129.143.253.133)2026101602
dns3.belwue.de (2001:7c0:0:253::133)2026101602

Checks

  • ✓ Serial 2026101602 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 30m, expire 28d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver dns.hfwu.de is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@hfwu.de #25
    The SOA RNAME hostmaster.hfwu.de means hostmaster@hfwu.de.
  • ✓ Date-based serial #26
    The serial 2026101602 follows the YYYYMMDDnn convention (2026-10-16).

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

16 records at the apex

Found

Read from
129.143.2.10:53
TypeValueTTL
SOAdns.hfwu.de. hostmaster.hfwu.de. 2026101602 21600 1800 2419200 864003600
NSdns3.belwue.de.600
NSdns1.belwue.de.600
A185.243.132.211600
AAAA2a03:2a00:1800:2::ac12:2ba7600
MX20 mx2.belwue.de.600
MX20 mx1.belwue.de.600
MX20 mx4.belwue.de.600
MX20 mx3.belwue.de.600
TXT"v=spf1 a:email-delivery.de mx:email-delivery.de include:email-delivery.de include:_spf.belwue.de include:de._netblocks.mimecast.com -all"600
TXT"MS=726B73C1FC1408870FA985D118FA11B2512F4374"600
TXT"google-gws-recovery-domain-verification=76473234"600
TXT"google-site-verification=1Ll7pQr13U0KvaOJIT-gdYUdAJ_H5pgxRqb567je8ik"600
TXT"zIbo1jkwgRdE8cIhejpBobyjH3sLQN6SPTRzEf7g4Kp8ZyK046VVZtaXvEg/ncJ7Nm7VWMyMbxPbg8+hioS2LA=="600
TXT"miro-verification=e25bfff4bc5ca97e1b44a8808c6fb3011178208b"600
TXT"0ed1fe018a2531a01f150e471381a413"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 10m, 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