marriott.de

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

eur1.akam.net, ns1-22.akam.net, ns1-7.akam.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
eur1.akam.net, ns1-22.akam.net, ns1-7.akam.net
NS in the zone
eur1.akam.net, ns1-22.akam.net, ns1-7.akam.net
NameserverAddressesNetwork (AS)Glue
eur1.akam.net2.16.130.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-22.akam.net193.108.91.22 2600:1401:2::16AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-7.akam.net193.108.91.7 2600:1401:2::7AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 3 nameservers #6
    Delegated to eur1.akam.net, ns1-22.akam.net, ns1-7.akam.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2600:1401:2::/48, while the other address family is spread over several networks.
    #10
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 1 address; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 4 addresses.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: eur1.akam.net.
    #13

Nameservers

warn

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
eur1.akam.net 2.16.130.64NOERROR, 9 ms, authoritativenoyes / yesrefused48878.31
ns1-22.akam.net 193.108.91.22NOERROR, 3 ms, authoritativenoyes / yesrefused41824.9
ns1-22.akam.net 2600:1401:2::16NOERROR, 3 ms, authoritativenoyes / yesrefused41824.7
ns1-7.akam.net 193.108.91.7NOERROR, 3 ms, authoritativenoyes / yesrefused41824.8
ns1-7.akam.net 2600:1401:2::7NOERROR, 4 ms, authoritativenoyes / yesrefused41824.9

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: eur1.akam.net: "48878.31"; ns1-22.akam.net: "41824.9"; ns1-22.akam.net: "41824.7"; ns1-7.akam.net: "41824.8"; ns1-7.akam.net: "41824.9". 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

info

serial 2007010564 · primary use4.akam.net

Found

Primary (MNAME)
use4.akam.net
Contact (RNAME)
infrahostmastergtm.marriott.com
Serial
2007010564
Refresh / retry
10800 s / 1800 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
eur1.akam.net (2.16.130.64)2007010564
ns1-22.akam.net (193.108.91.22)2007010564
ns1-22.akam.net (2600:1401:2::16)2007010564
ns1-7.akam.net (193.108.91.7)2007010564
ns1-7.akam.net (2600:1401:2::7)2007010564

Checks

  • ✓ Serial 2007010564 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 30m, expire 7d, negative TTL 15m.
  • i
    Hidden master
    The primary nameserver use4.akam.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact infrahostmastergtm@marriott.com #25
    The SOA RNAME infrahostmastergtm.marriott.com means infrahostmastergtm@marriott.com.
  • ✓ Date-based serial #26
    The serial 2007010564 follows the YYYYMMDDnn convention (2007-01-05).

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
2.16.130.64:53
TypeValueTTL
SOAuse4.akam.net. infrahostmastergtm.marriott.com. 2007010564 10800 1800 604800 900900
NSeur1.akam.net.900
NSns1-22.akam.net.900
NSns1-7.akam.net.900
A23.36.156.11420
MX10 marriott-de.mail.protection.outlook.com.900
TXT"facebook-domain-verification=dwhzxrdpab5ocd627ksunjhufh8xcl"900
TXT"ms=ms88734311"900
TXT"v=spf1 include:spf.marriott.com include:spf.protection.outlook.com -all"900
TXT"docusign=03399c35-17f3-4ab4-b906-88e889db7d7e"900
TXT"adobe-idp-site-verification=b58a812cb8a67904b7b89c5ba71e21242157d93cc4609f572f4d63398d2f1c95"900

Checks

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