schlaganfall-hilfe.de

Checked 22 October 2026, 00:01 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 4 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

ns0.iquer.net, ns1.iquer.net, ns2.iquer.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns0.iquer.net, ns1.iquer.net, ns2.iquer.net
NS in the zone
ns0.iquer.net, ns1.iquer.net, ns2.iquer.net
NameserverAddressesNetwork (AS)Glue
ns0.iquer.net185.57.243.2AS201955 IQUER-AS - iquer.net GmbH & Co KG, DE-
ns1.iquer.net81.20.85.14AS25260 QUALITYHOSTING-AS - QualityHosting GmbH, DE-
ns2.iquer.net85.236.54.102AS15456 INTERNETX-AS - InterNetX GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns0.iquer.net, ns1.iquer.net, ns2.iquer.net.
  • ✓ 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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS15456 (INTERNETX-AS - InterNetX GmbH, DE): 1 address; AS201955 (IQUER-AS - iquer.net GmbH & Co KG, DE): 1 address; AS25260 (QUALITYHOSTING-AS - QualityHosting GmbH, DE): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.iquer.net 185.57.243.2NOERROR, 6 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.4 (built Feb 13 2024 21:13:12 by mockbuild@localhost)
ns1.iquer.net 81.20.85.14NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.4 (built Feb 13 2024 21:13:12 by mockbuild@localhost)
ns2.iquer.net 85.236.54.102NOERROR, 10 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.4 (built Feb 13 2024 21:13:12 by mockbuild@localhost)

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns0.iquer.net: "PowerDNS Authoritative Server 4.8.4 (built Feb 13 2024 21:13:12 by mockbuild@localhost)"; ns1.iquer.net: "PowerDNS Authoritative Server 4.8.4 (built Feb 13 2024 21:13:12 by mockbuild@localhost)"; ns2.iquer.net: "PowerDNS Authoritative Server 4.8.4 (built Feb 13 2024 21:13:12 by mockbuild@localhost)". 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 2019052301 · primary ns0.iquer.net

Found

Primary (MNAME)
ns0.iquer.net
Contact (RNAME)
hostmaster.iquer.net
Serial
2019052301
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns0.iquer.net (185.57.243.2)2019052301
ns1.iquer.net (81.20.85.14)2019052301
ns2.iquer.net (85.236.54.102)2019052301

Checks

  • ✓ Serial 2019052301 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns0.iquer.net is one of the listed nameservers.
  • ✓ Contact hostmaster@iquer.net #25
    The SOA RNAME hostmaster.iquer.net means hostmaster@iquer.net.
  • ✓ Date-based serial #26
    The serial 2019052301 follows the YYYYMMDDnn convention (2019-05-23).

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

11 records at the apex

Found

Read from
185.57.243.2:53
TypeValueTTL
SOAns0.iquer.net. hostmaster.iquer.net. 2019052301 28800 7200 604800 864003600
NSns2.iquer.net.5166
NSns1.iquer.net.5166
NSns0.iquer.net.5166
A185.57.241.76300
MX10 schlaganfallhilfe-de03b.mail.protection.outlook.com.3600
TXT"brevo-code:1794cb194c59f7d81c4c60eb8b9d82ee"300
TXT"facebook-domain-verification=arv1k437tuibmy83883h0rz2er9l5y"300
TXT"google-site-verification=NU7o5oisN9XlwKBxHYSvpC8HoR1MojwsgV2GZ1QaH4I"300
TXT"v=spf1 include:_spf.iquer.net include:spf.protection.outlook.com include:spf.servicemail24.de ip4:145.228.190.192/27 -all"300
TXT"MS=ms57810782"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1h, NS 1h26m6s. The NS TTL at the parent is 1d and in the zone 1h26m6s; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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