cancom.de

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

info

ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info
NS in the zone
ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-06.azure-dns.com13.107.236.6 2603:1061:0:700::6AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2-06.azure-dns.net150.171.21.6 2620:1ec:8ec:700::6AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-06.azure-dns.org204.14.183.6 2a01:111:4000:700::6AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-06.azure-dns.info208.84.5.6 2620:1ec:bda:700::6AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info.
  • ✓ 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 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-06.azure-dns.com 13.107.236.6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-06.azure-dns.com 2603:1061:0:700::6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-06.azure-dns.net 150.171.21.6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-06.azure-dns.net 2620:1ec:8ec:700::6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-06.azure-dns.org 204.14.183.6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-06.azure-dns.org 2a01:111:4000:700::6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-06.azure-dns.info 208.84.5.6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-06.azure-dns.info 2620:1ec:bda:700::6NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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 2017051344 · primary ns1-06.azure-dns.com

Found

Primary (MNAME)
ns1-06.azure-dns.com
Contact (RNAME)
hostmaster.cancom.de
Serial
2017051344
Refresh / retry
28800 s / 3600 s
Expire
864000 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
ns1-06.azure-dns.com (13.107.236.6)2017051344
ns1-06.azure-dns.com (2603:1061:0:700::6)2017051344
ns2-06.azure-dns.net (150.171.21.6)2017051344
ns2-06.azure-dns.net (2620:1ec:8ec:700::6)2017051344
ns3-06.azure-dns.org (204.14.183.6)2017051344
ns3-06.azure-dns.org (2a01:111:4000:700::6)2017051344
ns4-06.azure-dns.info (208.84.5.6)2017051344
ns4-06.azure-dns.info (2620:1ec:bda:700::6)2017051344

Checks

  • ✓ Serial 2017051344 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 1h, expire 10d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-06.azure-dns.com is one of the listed nameservers.
  • ✓ Contact hostmaster@cancom.de #25
    The SOA RNAME hostmaster.cancom.de means hostmaster@cancom.de.
  • ✓ Date-based serial #26
    The serial 2017051344 follows the YYYYMMDDnn convention (2017-05-13).

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

26 records at the apex

Found

Read from
13.107.236.6:53
TypeValueTTL
SOAns1-06.azure-dns.com. hostmaster.cancom.de. 2017051344 28800 3600 864000 72003600
NSns1-06.azure-dns.com.172800
NSns2-06.azure-dns.net.172800
NSns3-06.azure-dns.org.172800
NSns4-06.azure-dns.info.172800
A78.47.144.137120
MX0 cancom-de.mail.protection.outlook.com.300
TXT"v=spf1 include:spf.protection.outlook.com include:_spf.pironet-ndh.com include:uhd.cancom.de ip4:217.5.129.98 ip4:167.89.63.5 ip4:195.82.68.217 a:em1143.cancom.com include:mailing.eqs.com include:_spf.rexx-suite.com -all"3600
TXT"MS=ms28273443"3600
TXT"WKNLLdgBlMMFcr4wiI2xnQNcshoqBQLb2Wp/+dmwECnXeUGzjj4rvOEnNYnh38RBCQjnL838f8ykAQfA/r1jUQ=="3600
TXT"atlassian-domain-verification=XF0xzI9/susMtnoiSJ8PQqeqTbRoECqMWiKCdGPBC9ZaedWWLM3hHalFZ8rCvgu/"3600
TXT"adobe-idp-site-verification=1dc967af4eb21419e9adbea4192430673c8cf078418c70d6fcedc4b629769d7d"3600
TXT"facebook-domain-verification=eua7qzlz8hps08aao4pzjcrnu05uu1"3600
TXT"teamviewer-sso-verification=7f87e140606b4103b240c80adecb329e"3600
TXT"atlassian-sending-domain-verification=3742228b-47be-4e80-b4b3-6c403d5f3233"3600
TXT"ecostruxure-it-verification=8418bea0-dc44-483c-b39c-655b5517aaf1"3600
TXT"1password-site-verification=GMRKEEVHXJFNXJPEAPLNZLRAHA"3600
TXT"jamf-site-verification=Ip_lGoeHfexqd4QEnY61dg"3600
TXT"fTkN6UM1kDQ/FmpQdWvXaf234A6CyQxH40PrEno/Q9Pnsu61qxnPXjSEDglfayvkgk9a2Uji1g1ExYSgvazN0A=="3600
TXT"google-site-verification=6MbY5-t81nEjgrytaT-1pLPRxSr2wuLouzfQgWqU8V0"3600
TXT"google-site-verification=QnXscmvYHtkAtQAvUavy7F_EApJBWiUM6UTaYOWjDZU"3600
TXT"anthropic-domain-verification-vnxqpe=PsRplgSeNST3PcM9TAbOB3yy2"3600
TXT"apple-domain-verification=UdkIi3ZfZ4iAuXM6"3600
TXT"00D1t000000vNcM=1TBbi00000003ab;00DhE000000DxVK=1TBhE00000006Gj;00DhE000000E3sT=1TBhE000000068f"3600
TXT"hpe-greenlake-domain-verification=57646642624a4730544c484179736635474665766975722d7a67715033707971"3600
TXT"_wokzjnuf7cm8k84p81fwmaplxoate5j"3600

Checks

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