hamburger-kunsthalle.de

Checked 21 October 2026, 22:41 UTC · via 8.8.8.8
!Passed with warnings
17 passed 5 warnings 0 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

ns1.uvensys.de, ns2.uvensys.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.uvensys.de, ns2.uvensys.de
NS in the zone
ns1.uvensys.de, ns2.uvensys.de
NameserverAddressesNetwork (AS)Glue
ns1.uvensys.de37.208.104.2 2a00:d0c0:d3:1::100AS58010 UVENSYS - uvensys GmbH, DE AS58010 UVENSYS - uvensys GmbH, DE37.208.104.2
ns2.uvensys.de37.208.110.2 2a00:d0c0:d4:1::100AS58010 UVENSYS - uvensys GmbH, DE AS58010 UVENSYS - uvensys GmbH, DE37.208.110.2

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.uvensys.de, ns2.uvensys.de.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns1.uvensys.de (glue 37.208.104.2, zone 37.208.104.2, 2a00:d0c0:d3:1::100); ns2.uvensys.de (glue 37.208.110.2, zone 37.208.110.2, 2a00:d0c0:d4:1::100). Update the glue at your registrar.
    #8
  • ✓ 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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS58010 (UVENSYS - uvensys GmbH, 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
ns1.uvensys.de 37.208.104.2NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns1.uvensys.de 2a00:d0c0:d3:1::100NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns2.uvensys.de 37.208.110.2NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns2.uvensys.de 2a00:d0c0:d4:1::100NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3

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: ns1.uvensys.de: "PowerDNS Authoritative Server 4.7.3"; ns2.uvensys.de: "PowerDNS Authoritative Server 4.7.3". 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

warn

serial 2026081102 · primary ns1.uvensys.de

Found

Primary (MNAME)
ns1.uvensys.de
Contact (RNAME)
support.uvensys.de
Serial
2026081102
Refresh / retry
86400 s / 3600 s
Expire
86400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.uvensys.de (37.208.104.2)2026081102
ns1.uvensys.de (2a00:d0c0:d3:1::100)2026081102
ns2.uvensys.de (37.208.110.2)2026081102
ns2.uvensys.de (2a00:d0c0:d4:1::100)2026081102

Checks

  • ✓ Serial 2026081102 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1d must be longer than refresh + retry. Current values: refresh 1d, retry 1h, expire 1d, negative TTL 1h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.uvensys.de is one of the listed nameservers.
  • ✓ Contact support@uvensys.de #25
    The SOA RNAME support.uvensys.de means support@uvensys.de.
  • ✓ Date-based serial #26
    The serial 2026081102 follows the YYYYMMDDnn convention (2026-08-11).

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

warn

11 records at the apex

Found

Read from
37.208.104.2:53
TypeValueTTL
SOAns1.uvensys.de. support.uvensys.de. 2026081102 86400 3600 86400 36003600
NSns2.uvensys.de.3600
NSns1.uvensys.de.3600
A37.208.107.22560
AAAA2a00:d0c0:c:19::1160
MX10 mx2.ondataport.de.3600
MX10 mx1.ondataport.de.3600
TXT"v=spf1 mx include:dataport.de ip4:37.208.111.158 ip4:37.208.107.225 -all"3600
TXT"nbq7mjc8zx07gqd29n5rz4x6tnp0d0tb"3600
TXT"MS=ms60064166"3600
TXT"MS=520D5162E4C05DF2225E1E442676CD4A7EA93F5B"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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