bertelsmann-stiftung.de

Checked 21 October 2026, 21:38 UTC · via 8.8.8.8
!Passed with warnings
25 passed 3 warnings 0 failed 5 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, 4 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, 4 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 2019061101 · primary ns0.iquer.net

Found

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

Serial per nameserver

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

Checks

  • ✓ Serial 2019061101 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 2019061101 follows the YYYYMMDDnn convention (2019-06-11).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
19529ECDSAP256SHA256 (13)SHA256 B44E0A9D325E0516…yes

DNSKEY in the zone

Key tagRoleAlgorithm
19529KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 19529 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

warn

19 records at the apex

Found

Read from
185.57.243.2:53
TypeValueTTL
SOAns0.iquer.net. hostmaster.iquer.net. 2019061101 28800 7200 604800 864003600
NSns1.iquer.net.6373
NSns2.iquer.net.6373
NSns0.iquer.net.6373
A185.57.241.76210
MX10 bertelsmannstiftung-de02i.mail.protection.outlook.com.3600
TXT"apple-domain-verification=XZQybtzYdTyrWknU"300
TXT"canva-site-verification=mRKahnQe323rhnL6LOaJYg"300
TXT"atlassian-domain-verification=FGifUt0/xMGgrJwJN6GshGzTIjDSYpyQhdwFFfhD8AxMsVZLVzN9wd41OX6Hrjga"300
TXT"docusign=77932888-6a13-461b-98e1-cef65e6b77e2"300
TXT"MS=ms42722630"300
TXT"MS=ms61467510"300
TXT"ZOOM_verify_0dw0DEpdU0CV8pS4kS0b3P"300
TXT"openai-domain-verification=dv-GAk4YfDGznSwJFcvXKbwu6ya"300
TXT"MS=ms73872518"300
TXT"adobe-idp-site-verification=ddb06c81-5737-4044-ba0e-d6bfca29da0b"300
TXT"d365mktkey=ffxUkTIkpYH7wLiQJMx3viNTaJJqZlohnetqsqxg6pkx"300
TXT"v=spf1 include:customers.clickdimensions.com include:_spf.iquer.net include:spf.protection.outlook.com include:spf.servicemail24.de include:_spf.eu.messagegears.net ip4:145.228.190.192/27 include:spf.mailjet.com -all"300
TXT"v=verifydomain MS=ms81956906"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (3m30s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h46m13s; resolvers may use either.
    #32
  • ✓ 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