lizzynet.de

Checked 21 October 2026, 23:20 UTC · via 8.8.8.8
✗Problems found
20 passed 2 warnings 1 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

ns.diginame.de, pdns02.domaincontrol.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.diginame.de, pdns02.domaincontrol.com
NS in the zone
ns.diginame.de, pdns02.domaincontrol.com
NameserverAddressesNetwork (AS)Glue
ns.diginame.de62.96.182.3AS8220 COLT - COLT Technology Services Group Limited, GB-
pdns02.domaincontrol.com173.201.78.50 2603:5:22e0::32AS44273 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: ns.diginame.de, pdns02.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 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS44273 (GODADDY-DNS - Host Europe GmbH, DE): 2 addresses; AS8220 (COLT - COLT Technology Services Group Limited, GB): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .de.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns.diginame.de.
    #13

Nameservers

fail

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.diginame.de 62.96.182.3NOERROR, 8 ms, authoritativenono / norefused-
pdns02.domaincontrol.com 173.201.78.50NOERROR, 3 ms, authoritativenoyes / yesrefused-
pdns02.domaincontrol.com 2603:5:22e0::32NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns.diginame.de (62.96.182.3): read tcp 46.225.38.91:58642->62.96.182.3:53: read: connection reset by peer.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns.diginame.de (62.96.182.3).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 1792074697 · primary ns.diginame.de

Found

Primary (MNAME)
ns.diginame.de
Contact (RNAME)
hostmaster.lizzynet.de
Serial
1792074697
Refresh / retry
16384 s / 2048 s
Expire
1048576 s
Negative TTL
2560 s

Serial per nameserver

NameserverSerial
ns.diginame.de (62.96.182.3)1792074697
pdns02.domaincontrol.com (173.201.78.50)1792074697
pdns02.domaincontrol.com (2603:5:22e0::32)1792074697

Checks

  • ✓ Serial 1792074697 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h33m4s, retry 34m8s, expire 291h16m16s, negative TTL 42m40s.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.diginame.de is one of the listed nameservers.
  • ✓ Contact hostmaster@lizzynet.de #25
    The SOA RNAME hostmaster.lizzynet.de means hostmaster@lizzynet.de.
  • ✓ Timestamp serial #26
    The serial 1792074697 is a Unix timestamp (2026-10-15 14:31 UTC).

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

8 records at the apex

Found

Read from
62.96.182.3:53
TypeValueTTL
SOAns.diginame.de. hostmaster.lizzynet.de. 1792074697 16384 2048 1048576 25602560
NSns.diginame.de.259200
NSpdns02.domaincontrol.com.259200
A93.191.167.26300
MX10 mailwall.bringe.digionline.de.86400
TXT"v=spf1 ip4:62.96.182.0/24 ip4:93.191.167.0/25 ?all"86400
TXT"MS=ms35661017"86400
TXT"google-site-verification=2wSKQejJIZrwkLtHsraETd3ABRppAZEmHTd0e4pJnCM"86400

Checks

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