rheuma-liga.de

Checked 22 October 2026, 00:00 UTC · via 8.8.8.8
!Passed with warnings
18 passed 1 warning 0 failed 10 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

ns1.ns-serve.net, ns2.ns-serve.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.ns-serve.net, ns2.ns-serve.net
NS in the zone
ns1.ns-serve.net, ns2.ns-serve.net
NameserverAddressesNetwork (AS)Glue
ns1.ns-serve.net195.191.92.140 2001:67c:2394:2::1001AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE-
ns2.ns-serve.net195.191.93.140 2001:67c:2394:4::1001AS25504 CRONON-AS - Vautron Rechenzentrum AG, DE AS25504 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.ns-serve.net, ns2.ns-serve.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:67c:2394::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS25504 (CRONON-AS - Vautron Rechenzentrum AG, DE): 4 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 .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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ns-serve.net 195.191.92.140NOERROR, 13 ms, authoritativenoyes / yesrefusedVautron
ns1.ns-serve.net 2001:67c:2394:2::1001NOERROR, 13 ms, authoritativenoyes / yesrefusedVautron
ns2.ns-serve.net 195.191.93.140NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns2.ns-serve.net 2001:67c:2394:4::1001NOERROR, 13 ms, authoritativenoyes / yesrefusedVautron

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.ns-serve.net: "Vautron"; ns2.ns-serve.net: "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

info

serial 1784883739 · primary ns.zone35.de

Found

Primary (MNAME)
ns.zone35.de
Contact (RNAME)
root.ns.zone35.de
Serial
1784883739
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.ns-serve.net (195.191.92.140)1784883739
ns1.ns-serve.net (2001:67c:2394:2::1001)1784883739
ns2.ns-serve.net (195.191.93.140)1784883739
ns2.ns-serve.net (2001:67c:2394:4::1001)1784883739

Checks

  • ✓ Serial 1784883739 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.
  • i
    Hidden master
    The primary nameserver ns.zone35.de is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact root@ns.zone35.de #25
    The SOA RNAME root.ns.zone35.de means root@ns.zone35.de.
  • ✓ Timestamp serial #26
    The serial 1784883739 is a Unix timestamp (2026-07-24 09:02 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

10 records at the apex

Found

Read from
195.191.92.140:53
TypeValueTTL
SOAns.zone35.de. root.ns.zone35.de. 1784883739 10800 3600 604800 360086400
NSns1.ns-serve.net.3600
NSns2.ns-serve.net.3600
A88.198.54.1883600
MX40 mx04.hornetsecurity.com.3600
MX20 mx02.hornetsecurity.com.3600
MX10 mx01.hornetsecurity.com.3600
MX30 mx03.hornetsecurity.com.3600
TXT"MS=ms19630436"3600
TXT"v=spf1 a ip6:2a01:4f8:221:4614::2/64 ip6:2a01:4f8:c010:9220::/64 ip4:162.55.163.52 ip4:88.198.54.188 ip4:87.139.146.227 ip4:192.0.2.100/31 include:_spf.zimpel.de include:spf.hornetsecurity.com include:spf.protection.outlook.com ip4:87.138.196.203 ~all"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