gealan.de

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

warn

ns81.domaincontrol.com, ns82.domaincontrol.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns81.domaincontrol.com, ns82.domaincontrol.com
NS in the zone
ns81.domaincontrol.com, ns82.domaincontrol.com
NameserverAddressesNetwork (AS)Glue
ns81.domaincontrol.com97.74.101.32AS26496 AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC, US-
ns82.domaincontrol.com173.201.69.32AS44273 GODADDY-DNS - Host Europe GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns81.domaincontrol.com, ns82.domaincontrol.com.
    #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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS26496 (AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC, US): 1 address; AS44273 (GODADDY-DNS - Host Europe GmbH, DE): 1 address.
  • i
    All nameserver names under .com
    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

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns81.domaincontrol.com 97.74.101.32NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns82.domaincontrol.com 173.201.69.32NOERROR, 3 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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 2026101800 · primary ns81.domaincontrol.com

Found

Primary (MNAME)
ns81.domaincontrol.com
Contact (RNAME)
dns.jomax.net
Serial
2026101800
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns81.domaincontrol.com (97.74.101.32)2026101800
ns82.domaincontrol.com (173.201.69.32)2026101800

Checks

  • ✓ Serial 2026101800 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns81.domaincontrol.com is one of the listed nameservers.
  • ✓ Contact dns@jomax.net #25
    The SOA RNAME dns.jomax.net means dns@jomax.net.
  • ✓ Date-based serial #26
    The serial 2026101800 follows the YYYYMMDDnn convention (2026-10-18).

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

26 records at the apex

Found

Read from
97.74.101.32:53
TypeValueTTL
SOAns81.domaincontrol.com. dns.jomax.net. 2026101800 28800 7200 604800 6003600
NSns82.domaincontrol.com.3600
NSns81.domaincontrol.com.3600
A20.105.224.153600
MX10 smtp1.veka.com.3600
MX10 smtp2.veka.com.3600
MX10 smtp3.veka.com.3600
TXT"webexdomainverification.51IQC=377fc330-271b-4a72-bc3e-0496da6f330f"3600
TXT"google-site-verification=Lv2CSdGzyz8ZUZ4By_FhkdZT_Wa-koLZEUoUFQNqF2A"3600
TXT"have-i-been-pwned-verification=dweb_ynn55iik7w9t022cap1a8ife"3600
TXT"docusign=db8c5f49-e925-4ec1-a7d1-630120da3da2"3600
TXT"AD14EB18D92EEFC1EC6328D0D88841352DA6A30D908B805EC8931666AC373177"3600
TXT"openai-domain-verification=dv-POallRwVTHyOkBTq3hOq0Txt"3600
TXT"atlassian-domain-verification=4PQKDZTn0s6kO/8YpOzDYkMbc6C44xRX6Vq1XRQjLpKQkGr5QT/kMLdVUym0aacJ"3600
TXT"cisco-ci-domain-verification=b34eb497c716d3ec9bf1910b1f355d5aa10d9de4c715b04c7b383ed183c962a"3600
TXT"hibp-verify=dweb_yxymbuh39cotsp6tlle5dmzi"3600
TXT"anthropic-domain-verification-tggmf0=ZBwBo0JFo5F2JB3ka2DEouAIh"3600
TXT"geaken13prodmvc.azurewebsites.net"3600
TXT"brevo-code:6d01dfd7bea1ac53ccfd54ce8fbe7be4"3600
TXT"apple-domain-verification=zeHjsK024yLA888A"3600
TXT"ajra7u004ti84jlrimjovqe0r2"3600
TXT"v=spf1 mx a:mail1.veka.com include:spf.protection.outlook.com include:spf.sendinblue.com include:_spf.cmail.ondemand.com include:spf.mailjet.com include:_spf.pixelpark.eu include:spf.eu.signature365.net ip4:185.254.60.9 ip6:2001:67c:2018::6009 ~all"3600
TXT"knowbe4-site-verification=e37f35edfb9a221e0cb1838173152e26"3600
TXT"make-domain-verification=50c8d070-87a3-41fa-8395-e1f8165c45a4"3600
TXT"MS=ms23589621"3600
TXT"epg-domain-verification=44e6a807-6a81-4691-83c7-838e155ab019"3600

Checks

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