idw.de

Checked 21 October 2026, 22:51 UTC · via 8.8.8.8
!Passed with warnings
21 passed 2 warnings 0 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

ns1.boreus.de, ns2.boreus.de, ns3.boreus.de, ns4.boreus.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.boreus.de, ns2.boreus.de, ns3.boreus.de, ns4.boreus.de
NS in the zone
ns1.boreus.de, ns2.boreus.de, ns3.boreus.de, ns4.boreus.de
NameserverAddressesNetwork (AS)Glue
ns1.boreus.de208.82.72.7AS205411 BOREUS - WIIT AG, DE208.82.72.7
ns2.boreus.de185.21.124.250AS205411 BOREUS - WIIT AG, DE185.21.124.250
ns3.boreus.de185.21.125.2AS205411 BOREUS - WIIT AG, DE185.21.125.2
ns4.boreus.de18.196.15.34 2a05:d014:5c9:5a00:10ed:d525:2691:834eAS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US18.196.15.34 2a05:d014:5c9:5a00:10ed:d525:2691:834e

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.boreus.de, ns2.boreus.de, ns3.boreus.de, ns4.boreus.de.
  • ✓ 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 4 IPv4 /24s and 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 addresses; AS205411 (BOREUS - WIIT AG, DE): 3 addresses.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.boreus.de, ns2.boreus.de, ns3.boreus.de.
    #13

Nameservers

info

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.boreus.de 208.82.72.7NOERROR, 18 ms, authoritativenoyes / yesrefusednone
ns2.boreus.de 185.21.124.250NOERROR, 19 ms, authoritativenoyes / yesrefusednone
ns3.boreus.de 185.21.125.2NOERROR, 18 ms, authoritativenoyes / yesrefusednone
ns4.boreus.de 18.196.15.34NOERROR, 4 ms, authoritativenoyes / yesrefusednone
ns4.boreus.de 2a05:d014:5c9:5a00:10ed:d525:2691:834eNOERROR, 4 ms, authoritativenoyes / yesrefusednone

Checks

  • ✓ All respond #14
    All 5 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.boreus.de: "none"; ns2.boreus.de: "none"; ns3.boreus.de: "none"; ns4.boreus.de: "none".
    #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 2026091000 · primary ns1.boreus.de

Found

Primary (MNAME)
ns1.boreus.de
Contact (RNAME)
hostmaster.boreus.de
Serial
2026091000
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.boreus.de (208.82.72.7)2026091000
ns2.boreus.de (185.21.124.250)2026091000
ns3.boreus.de (185.21.125.2)2026091000
ns4.boreus.de (18.196.15.34)2026091000
ns4.boreus.de (2a05:d014:5c9:5a00:10ed:d525:2691:834e)2026091000

Checks

  • ✓ Serial 2026091000 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.boreus.de is one of the listed nameservers.
  • ✓ Contact hostmaster@boreus.de #25
    The SOA RNAME hostmaster.boreus.de means hostmaster@boreus.de.
  • ✓ Date-based serial #26
    The serial 2026091000 follows the YYYYMMDDnn convention (2026-09-10).

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

warn

11 records at the apex

Found

Read from
208.82.72.7:53
TypeValueTTL
SOAns1.boreus.de. hostmaster.boreus.de. 2026091000 10800 3600 604800 1080060
NSns4.boreus.de.60
NSns3.boreus.de.60
NSns1.boreus.de.60
NSns2.boreus.de.60
A208.82.72.4760
MX10 idw-de.mail.protection.outlook.com.60
TXT"v=spf1 mx ip4:208.82.73.189 ip4:185.243.10.111 ip4:213.61.151.93 ip4:185.243.10.28 ip4:213.61.151.91 " "include:spf.protection.outlook.com include:spf-de.emailsignatures365.com " "include:_spf.zimpel.de a:mail.fp-sign.com include:_spf.sendnode.com " "include:spf.prod.universal-messenger.cloud ~all"60
TXT"tmes=dff192b65b32e02a65294176514ed5b7"60
TXT"MS=ms12356467"60
TXT"google-site-verification=M9ZMOL7F8wuuGvixChGAlZ6EoPeZ0QFTbitZIDcjPbI"60

Checks

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