xlx747.de

Checked 22 October 2026, 01:10 UTC · via 8.8.8.8
!Passed with warnings
19 passed 2 warnings 0 failed 8 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

ns1.n5q.de, ns2.n5q.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.n5q.de, ns2.n5q.de
NS in the zone
ns1.n5q.de, ns2.n5q.de
NameserverAddressesNetwork (AS)Glue
ns1.n5q.de195.191.92.11AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE-
ns2.n5q.de195.191.93.11AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.n5q.de, ns2.n5q.de.
    #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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS25504 (CRONON-AS - Vautron Rechenzentrum AG, DE): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.n5q.de 195.191.92.11NOERROR, 13 ms, authoritativenoyes / yesrefusedVautron
ns2.n5q.de 195.191.93.11NOERROR, 18 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.n5q.de: "Vautron".
    #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 1790597792 · primary ns1.n5q.de

Found

Primary (MNAME)
ns1.n5q.de
Contact (RNAME)
root.ns1.n5q.de
Serial
1790597792
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.n5q.de (195.191.92.11)1790597792
ns2.n5q.de (195.191.93.11)1790597792

Checks

  • ✓ Serial 1790597792 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.n5q.de is one of the listed nameservers.
  • ✓ Contact root@ns1.n5q.de #25
    The SOA RNAME root.ns1.n5q.de means root@ns1.n5q.de.
  • ✓ Timestamp serial #26
    The serial 1790597792 is a Unix timestamp (2026-09-28 12:16 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

6 records at the apex

Found

Read from
195.191.92.11:53
TypeValueTTL
SOAns1.n5q.de. root.ns1.n5q.de. 1790597792 10800 3600 604800 3600300
NSns1.n5q.de.300
NSns2.n5q.de.300
A78.47.190.213300
MX10 mail13.netbeat.de.300
TXT"v=spf1 a mx ip4:46.151.162.0/24 ip4:46.151.164.0/24 ip4:83.243.58.0/24 ip6:2a00:19e0:c0de::/48 ?all"300

Checks

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