toll-collect.de

Checked 22 October 2026, 00:41 UTC · via 8.8.8.8
!Passed with warnings
24 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

warn

ns1.open-telekom-cloud.com, ns2.open-telekom-cloud.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.open-telekom-cloud.com, ns2.open-telekom-cloud.com
NS in the zone
ns1.open-telekom-cloud.com, ns2.open-telekom-cloud.com
NameserverAddressesNetwork (AS)Glue
ns1.open-telekom-cloud.com80.158.48.19AS6878 AS6878 - T-Systems International GmbH, DE-
ns2.open-telekom-cloud.com93.188.242.252AS34086 SCZN-AS - T-Systems International GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.open-telekom-cloud.com, ns2.open-telekom-cloud.com.
    #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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS34086 (SCZN-AS - T-Systems International GmbH, DE): 1 address; AS6878 (AS6878 - T-Systems International GmbH, DE): 1 address.
  • i
    All nameserver names under .com
    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

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.open-telekom-cloud.com 80.158.48.19NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns2.open-telekom-cloud.com 93.188.242.252NOERROR, 12 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 1 · primary ns1.open-telekom-cloud.com

Found

Primary (MNAME)
ns1.open-telekom-cloud.com
Contact (RNAME)
dl-otc-domains.telekom.de
Serial
1
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.open-telekom-cloud.com (80.158.48.19)1
ns2.open-telekom-cloud.com (93.188.242.252)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.open-telekom-cloud.com is one of the listed nameservers.
  • ✓ Contact dl-otc-domains@telekom.de #25
    The SOA RNAME dl-otc-domains.telekom.de means dl-otc-domains@telekom.de.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
8 October 2027

DNSKEY in the zone

Key tagRoleAlgorithm
50008ZSK (256)ECDSAP256SHA256 (13)
29033KSK (257)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2027-10-08 #30
    The earliest DNSKEY/SOA signature expires at 2027-10-08 04:45 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

info

15 records at the apex

Found

Read from
80.158.48.19:53
TypeValueTTL
SOAns1.open-telekom-cloud.com. dl-otc-domains.telekom.de. 1 7200 900 1209600 300300
NSns2.open-telekom-cloud.com.172800
NSns1.open-telekom-cloud.com.172800
A80.158.4.78300
MX10 mailx1.toll-collect.de.300
MX10 mailx2.toll-collect.de.300
TXT"adobe-idp-site-verification=a5adc162a82702005c61628a4e94f100678b13b2012e9bc2f8001a48ae216e4c"300
TXT"cisco-ci-domain-verification=c1adb1034b4ae631a2015f41f1aeb6fd5583f2f83a972b7c30a9eb881b27e9a"300
TXT"v=spf1 include:_spf.zimpel.de ip4:193.158.50.97 ip4:193.158.50.98 ip4:80.158.29.239 ip4:80.158.30.19 a:spf.mas.t-systems-service.com ip4:62.55.182.68 " "include:spf.mailjet.com ip4:87.253.232.0/24 ip4:87.253.233.0/24 ip4:87.253.234.0/24 ip4:87.253.235.0/24 ip4:87.253.236.0/24 ip4:87.253.237.0/24 ip4:87.253.238.0/24 ip4:87.253.239.0/24 -all"300
TXT"_b0omladf2coqcr3i8ox4rd2utnhc1cf"300
TXT"_wul91lovkus5ih7v0gjsmsrhlney3fo"300
TXT"apple-domain-verification=owQAiqGl1RRGRlar"300
TXT"MS=945CBF89A63C0CF4686DB079DD92991D82BC735D"300
TXT"swisssign-check=8RszafTu7HnOLIM9-tLcSMRAHiM"300
TXT"miro-verification=6dafadfe973cd63aca95df96fcbaec7695269537"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 2d. The NS TTL at the parent is 1d and in the zone 2d; 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