gepa.de

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

ns51.domaincontrol.com, ns52.domaincontrol.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns51.domaincontrol.com, ns52.domaincontrol.com
NS in the zone
ns51.domaincontrol.com, ns52.domaincontrol.com
NameserverAddressesNetwork (AS)Glue
ns51.domaincontrol.com97.74.105.26 2603:5:2192::1aAS26496 AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC, US AS44273 GODADDY-DNS - Host Europe GmbH, DE-
ns52.domaincontrol.com173.201.73.26 2603:5:2292::1aAS44273 GODADDY-DNS - Host Europe GmbH, DE AS44273 GODADDY-DNS - Host Europe GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns51.domaincontrol.com, ns52.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 2 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): 3 addresses.
  • 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns51.domaincontrol.com 97.74.105.26NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns51.domaincontrol.com 2603:5:2192::1aNOERROR, 3 ms, authoritativenoyes / yesrefused-
ns52.domaincontrol.com 173.201.73.26NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns52.domaincontrol.com 2603:5:2292::1aNOERROR, 4 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 2026102005 · primary ns51.domaincontrol.com

Found

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

Serial per nameserver

NameserverSerial
ns51.domaincontrol.com (97.74.105.26)2026102005
ns51.domaincontrol.com (2603:5:2192::1a)2026102005
ns52.domaincontrol.com (173.201.73.26)2026102005
ns52.domaincontrol.com (2603:5:2292::1a)2026102005

Checks

  • ✓ Serial 2026102005 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 ns51.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 2026102005 follows the YYYYMMDDnn convention (2026-10-20).

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
97.74.105.26:53
TypeValueTTL
SOAns51.domaincontrol.com. dns.jomax.net. 2026102005 28800 7200 604800 6003600
NSns52.domaincontrol.com.3600
NSns51.domaincontrol.com.3600
A178.77.82.15986400
AAAA2a01:488:42:1000:b24d:529f:ff6f:165786400
MX100 gepa-de.mail.protection.outlook.com.86400
TXT"MS=ms84244650"86400
TXT"google-site-verification=1tZDRbmW9U0zgDUyj6TsO9_-2vPKb9HnKj9g55yMhC8"86400
TXT"apple-domain-verification=JafhugULYgF3mhhB"86400
TXT"v=spf1 mx a ip4:178.77.82.159 ip4:18.211.9.206 ip4:62.153.69.250 ip4:62.153.69.252 ip4:62.153.69.254 ip4:213.95.132.52 ip4:213.155.74.87 ip4:213.155.74.23 ip4:213.155.74.157 ip4:213.155.74.133 include:spf.protection.outlook.com include:spf.docuguide.com i" "nclude:spf-de.emailsignatures365.com ~all"86400
TXT"d365mktkey=tQnMdFNx1P07NVxNAQQZ1clEkZRxLLXaxitQzzeBKqAx"86400
TXT"facebook-domain-verification=r424bn17hacv45ygtmyuvujlvcp57h"86400
TXT"msfpkey=ql65chxc3bjr5y8iux1v2l8h"86400
TXT"kGmZ51I6s2rzXYgq4q539EshnlJWcAXy4qETwX3IMtDzKcqeFTd0RKZtEOek9POAz3nL1RhCz1+nH+WbRxTauQ=="86400
TXT"pjejd9bki79ngqdijmdhicgg6j"86400
TXT"d365mktkey=wwjnewecxkryhlnczm8cu2xp"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, AAAA 1d, MX 1d, 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