dgq.de

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

info

nameserver-1-de.maxcluster.net, nameserver-2-de.maxcluster.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
nameserver-1-de.maxcluster.net, nameserver-2-de.maxcluster.net
NS in the zone
nameserver-1-de.maxcluster.net, nameserver-2-de.maxcluster.net
NameserverAddressesNetwork (AS)Glue
nameserver-1-de.maxcluster.net62.113.231.252 2a00:f48:1008::231:252:10AS47447 TTM - 23M GmbH, DE AS47447 TTM - 23M GmbH, DE-
nameserver-2-de.maxcluster.net116.202.5.160 2a01:4f8:c01f:63::10AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: nameserver-1-de.maxcluster.net, nameserver-2-de.maxcluster.net.
    #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: AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 2 addresses; AS47447 (TTM - 23M GmbH, DE): 2 addresses.
  • i
    All nameserver names under .net
    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
nameserver-1-de.maxcluster.net 62.113.231.252NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1
nameserver-1-de.maxcluster.net 2a00:f48:1008::231:252:10NOERROR, 4 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1
nameserver-2-de.maxcluster.net 116.202.5.160NOERROR, 6 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1
nameserver-2-de.maxcluster.net 2a01:4f8:c01f:63::10NOERROR, 6 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.1

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: nameserver-1-de.maxcluster.net: "PowerDNS Authoritative Server 4.1.1"; nameserver-2-de.maxcluster.net: "PowerDNS Authoritative Server 4.1.1". 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

pass

serial 2026100606 · primary nameserver-1-de.maxcluster.net

Found

Primary (MNAME)
nameserver-1-de.maxcluster.net
Contact (RNAME)
info.maxcluster.net
Serial
2026100606
Refresh / retry
3600 s / 1000 s
Expire
1209600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
nameserver-1-de.maxcluster.net (62.113.231.252)2026100606
nameserver-1-de.maxcluster.net (2a00:f48:1008::231:252:10)2026100606
nameserver-2-de.maxcluster.net (116.202.5.160)2026100606
nameserver-2-de.maxcluster.net (2a01:4f8:c01f:63::10)2026100606

Checks

  • ✓ Serial 2026100606 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 16m40s, expire 14d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver nameserver-1-de.maxcluster.net is one of the listed nameservers.
  • ✓ Contact info@maxcluster.net #25
    The SOA RNAME info.maxcluster.net means info@maxcluster.net.
  • ✓ Date-based serial #26
    The serial 2026100606 follows the YYYYMMDDnn convention (2026-10-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

15 records at the apex

Found

Read from
62.113.231.252:53
TypeValueTTL
SOAnameserver-1-de.maxcluster.net. info.maxcluster.net. 2026100606 3600 1000 1209600 60086400
NSnameserver-2-de.maxcluster.net.86400
NSnameserver-1-de.maxcluster.net.86400
A185.88.213.212300
MX0 dgq-de.mail.protection.outlook.com.3600
TXT"pardot856023=31419b04829a8277e4e9730dff4a9ac39082d7472345cb72b5a08c97c1d5c3b5"300
TXT"MS=ms35992196"86400
TXT"pardot856023=1052de7b56fe48f10573cfbe417545d2f55a7935bb0b991dfd8771b1a39c3b42"3600
TXT"facebook-domain-verification=avpna78nztcqe5w2smso7ykhxesr0m"300
TXT"9cfn1d1sco0m92r3vc7omvt01i"300
TXT"v=spf1 a mx include:spf.protection.outlook.com include:_spf.act-on.net include:spf.de.umantis.com include:_spf.salesforce.com include:spf.tixxt.com ip4:185.169.57.226 -all"300
TXT"brevo-code:dd16314b8945254dbfac0b5dfc7773af"300
TXT"apple-domain-verification=E4owOWwmTejRuVHZ"300
TXT"anthropic-domain-verification-6c77nz=3KmcR5ApQtYRnxNKgfM9PUIEc"300
TXT"linkedin-site-verification=bb2d6f6c-d822-42b3-99a8-a9ba99d00d63"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1h, NS 1d.
  • ✓ 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