dmsb.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
!Passed with warnings
21 passed 1 warning 0 failed 7 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.comtrance.de, ns2.comtrance.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.comtrance.de, ns2.comtrance.de
NS in the zone
ns1.comtrance.de, ns2.comtrance.de
NameserverAddressesNetwork (AS)Glue
ns1.comtrance.de217.160.81.161 2001:8d8:fe:53:217:160:81:161AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE217.160.81.161 2001:8d8:fe:53:217:160:81:161
ns2.comtrance.de185.132.35.161 2607:f1c0:fe:53:185:132:35:161AS15418 IONOS-ANYCAST - Fasthosts Internet Limited, GB AS15418 IONOS-ANYCAST - Fasthosts Internet Limited, GB185.132.35.161 2607:f1c0:fe:53:185:132:35:161

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.comtrance.de, ns2.comtrance.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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15418 (IONOS-ANYCAST - Fasthosts Internet Limited, GB): 2 addresses; AS8560 (IONOS-AS - IONOS SE, DE): 2 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.comtrance.de 217.160.81.161NOERROR, 9 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns1.comtrance.de 2001:8d8:fe:53:217:160:81:161NOERROR, 13 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.comtrance.de 185.132.35.161NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.comtrance.de 2607:f1c0:fe:53:185:132:35:161NOERROR, 7 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

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.comtrance.de: "Served by PowerDNS - https://www.powerdns.com/"; ns2.comtrance.de: "Served by PowerDNS - https://www.powerdns.com/".
    #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 2022111625 · primary ns1.comtrance.de

Found

Primary (MNAME)
ns1.comtrance.de
Contact (RNAME)
domain.comtrance.net
Serial
2022111625
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.comtrance.de (217.160.81.161)2022111625
ns1.comtrance.de (2001:8d8:fe:53:217:160:81:161)2022111625
ns2.comtrance.de (185.132.35.161)2022111625
ns2.comtrance.de (2607:f1c0:fe:53:185:132:35:161)2022111625

Checks

  • ✓ Serial 2022111625 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.comtrance.de is one of the listed nameservers.
  • ✓ Contact domain@comtrance.net #25
    The SOA RNAME domain.comtrance.net means domain@comtrance.net.
  • ✓ Date-based serial #26
    The serial 2022111625 follows the YYYYMMDDnn convention (2022-11-16).

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

9 records at the apex

Found

Read from
217.160.81.161:53
TypeValueTTL
SOAns1.comtrance.de. domain.comtrance.net. 2022111625 28800 7200 604800 300300
NSns1.comtrance.de.86400
NSns2.comtrance.de.86400
A81.173.115.182300
MX0 dmsb-de.mail.protection.outlook.com.300
TXT"atlassian-domain-verification=tEObYei5kNZjumBoBujMazLfz7fDfvuYiRkCtblnavFFixIm81Ahn79eXgXk9d3s"86400
TXT"MS=ms38672720"3600
TXT"anthropic-domain-verification-bmr34q=VAsK2gJ0dI7aVO1XVjn7kSQDP"600
TXT"v=spf1 a mx ip4:85.215.48.221 ip4:217.160.117.197 ip4:212.132.90.67 ip4:212.132.90.99 ip4:212.227.51.151 ip4:185.219.102.52 ip4:217.160.12.158 include:spf-de.emailsignatures365.com include:spfhard.crsend.com include:spf.protection.outlook.com -all"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 1d.
  • ✓ 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