hamburg-messe.de

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

ns1.arcor-ip.de, ns2.arcor-ip.de, ns3.arcor-ip.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.arcor-ip.de, ns2.arcor-ip.de, ns3.arcor-ip.de
NS in the zone
ns1.arcor-ip.de, ns2.arcor-ip.de, ns3.arcor-ip.de
NameserverAddressesNetwork (AS)Glue
ns1.arcor-ip.de145.253.2.144 2a01:860:0:202::53AS3209 VODANET - Vodafone GmbH, DE AS3209 VODANET - Vodafone GmbH, DE145.253.2.144 2a01:860:0:202::53
ns2.arcor-ip.de145.253.3.16 2a01:860:0:203::53AS3209 VODANET - Vodafone GmbH, DE AS3209 VODANET - Vodafone GmbH, DE145.253.3.16 2a01:860:0:203::53
ns3.arcor-ip.de145.253.3.20 2a01:860:0:204::53AS3209 VODANET - Vodafone GmbH, DE AS3209 VODANET - Vodafone GmbH, DE145.253.3.20 2a01:860:0:204::53

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.arcor-ip.de, ns2.arcor-ip.de, ns3.arcor-ip.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a01:860::/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 (AS3209 (VODANET - Vodafone GmbH, DE): 6 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

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.arcor-ip.de 145.253.2.144NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.arcor-ip.de 2a01:860:0:202::53NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.arcor-ip.de 145.253.3.16NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.arcor-ip.de 2a01:860:0:203::53NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns3.arcor-ip.de 145.253.3.20NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns3.arcor-ip.de 2a01:860:0:204::53NOERROR, 9 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✓ 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.
  • ✓ 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 2026070600 · primary ns1.arcor-ip.de

Found

Primary (MNAME)
ns1.arcor-ip.de
Contact (RNAME)
hostmaster.adm.arcor.net
Serial
2026070600
Refresh / retry
28800 s / 14400 s
Expire
1814400 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns1.arcor-ip.de (145.253.2.144)2026070600
ns1.arcor-ip.de (2a01:860:0:202::53)2026070600
ns2.arcor-ip.de (145.253.3.16)2026070600
ns2.arcor-ip.de (2a01:860:0:203::53)2026070600
ns3.arcor-ip.de (145.253.3.20)2026070600
ns3.arcor-ip.de (2a01:860:0:204::53)2026070600

Checks

  • ✓ Serial 2026070600 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 4h, expire 21d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.arcor-ip.de is one of the listed nameservers.
  • ✓ Contact hostmaster@adm.arcor.net #25
    The SOA RNAME hostmaster.adm.arcor.net means hostmaster@adm.arcor.net.
  • ✓ Date-based serial #26
    The serial 2026070600 follows the YYYYMMDDnn convention (2026-07-06).

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
145.253.2.144:53
TypeValueTTL
SOAns1.arcor-ip.de. hostmaster.adm.arcor.net. 2026070600 28800 14400 1814400 7200600
NSns2.arcor-ip.de.600
NSns1.arcor-ip.de.600
NSns3.arcor-ip.de.600
A52.18.147.128600
MX1 hamburgmesse-de01i.mail.protection.outlook.com.600
TXT"amazonses:fN8KQfySMJuy7+luCeR3CBSFAhdTXeKGGVYzsgxI6MU="86400
TXT"apple-domain-verification=L3J5m7GOoobxflBj"86400
TXT"MS=ms65533365"86400
TXT"atlassian-domain-verification=78V0Ar3ynW0jhD8V3MBue7FEyMNv7H756YBF3DtevLJOdj1PFaEjEut9FkcMDJ2m"86400
TXT"v=spf1 a:spf.mas.t-systems-service.com ip4:88.79.197.24 ip4:88.79.197.25 ip4:195.30.123.178 include:spf.protection.outlook.com include:spf.de.umantis.com include:spf.mailjet.com include:_spf.eu.mailgun.org include:amazonses.com ~all"86400

Checks

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