marriott.fr

Checked 22 October 2026, 04:15 UTC · via 8.8.8.8
!Passed with warnings
21 passed 4 warnings 0 failed 6 info

Registration

warn

.fr country-code · CSC CORPORATE DOMAINS INC. · expires 2026-11-19

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
CSC CORPORATE DOMAINS INC.
Registered
19 November 2004
Last changed
21 November 2025
Expires
19 November 2026
Status
server update prohibited, server transfer prohibited, server delete prohibited, server recover prohibited
Registry nameservers
eur1.akam.net, eur3.akam.net, eur4.akam.net, ns1-22.akam.net, ns1-7.akam.net, usc1.akam.net, usc2.akam.net, use4.akam.net
RDAP server
https://rdap.nic.fr/

Checks

  • i
    .fr 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
    .fr is delegated in the root zone and DNSSEC-signed.
  • !
    Expires in 28 days
    The registration expires on 2026-11-19. Make sure it is renewed.
    #3
  • ✓ Transfer locked #4
    Registry status: server update prohibited, server transfer prohibited, server delete prohibited, server recover prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

eur1.akam.net, eur3.akam.net, eur4.akam.net, ns1-22.akam.net, ns1-7.akam.net, usc1.akam.net, usc2.akam.net, use4.akam.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
eur1.akam.net, eur3.akam.net, eur4.akam.net, ns1-22.akam.net, ns1-7.akam.net, usc1.akam.net, usc2.akam.net, use4.akam.net
NS in the zone
eur1.akam.net, eur3.akam.net, eur4.akam.net, ns1-22.akam.net, ns1-7.akam.net, usc1.akam.net, usc2.akam.net, use4.akam.net
NameserverAddressesNetwork (AS)Glue
eur1.akam.net2.16.130.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur3.akam.net95.100.174.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur4.akam.net84.53.139.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-
usc1.akam.net95.100.168.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usc2.akam.net184.26.160.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use4.akam.net23.211.133.65AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 8 nameservers #6
    Delegated to eur1.akam.net, eur3.akam.net, eur4.akam.net, ns1-22.akam.net, ns1-7.akam.net, usc1.akam.net, usc2.akam.net, use4.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): 9 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, eur3.akam.net, eur4.akam.net, usc1.akam.net, usc2.akam.net, use4.akam.net.
    #13

Nameservers

warn

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
eur1.akam.net 2.16.130.64NOERROR, 7 ms, authoritativenoyes / yesrefused48878.32
eur3.akam.net 95.100.174.64NOERROR, 10 ms, authoritativenoyes / yesrefused48878.30
eur4.akam.net 84.53.139.64NOERROR, 3 ms, authoritativenoyes / yesrefused41824.11
ns1-22.akam.net 193.108.91.22NOERROR, 10 ms, authoritativenoyes / yesrefused41824.5
ns1-22.akam.net 2600:1401:2::16NOERROR, 10 ms, authoritativenoyes / yesrefused41824.10
ns1-7.akam.net 193.108.91.7NOERROR, 10 ms, authoritativenoyes / yesrefused41824.8
ns1-7.akam.net 2600:1401:2::7NOERROR, 11 ms, authoritativenoyes / yesrefused41824.11
usc1.akam.net 95.100.168.64NOERROR, 10 ms, authoritativenoyes / yesrefused41824.10
usc2.akam.net 184.26.160.64NOERROR, 11 ms, authoritativenoyes / yesrefused48878.27
use4.akam.net 23.211.133.65NOERROR, 9 ms, authoritativenoyes / yesrefused48878.32

Checks

  • ✓ All respond #14
    All 10 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.32"; eur3.akam.net: "48878.30"; eur4.akam.net: "41824.11"; ns1-22.akam.net: "41824.5"; ns1-22.akam.net: "41824.10"; ns1-7.akam.net: "41824.8"; ns1-7.akam.net: "41824.11"; usc1.akam.net: "41824.10"; usc2.akam.net: "48878.27"; use4.akam.net: "48878.32". 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

warn

serial 30 · primary ns-cloud-e1.googledomains.com

Found

Primary (MNAME)
ns-cloud-e1.googledomains.com
Contact (RNAME)
cloud-dns-hostmaster.google.com
Serial
30
Refresh / retry
21600 s / 3600 s
Expire
259200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
eur1.akam.net (2.16.130.64)30
eur3.akam.net (95.100.174.64)30
eur4.akam.net (84.53.139.64)30
ns1-22.akam.net (193.108.91.22)30
ns1-22.akam.net (2600:1401:2::16)30
ns1-7.akam.net (193.108.91.7)30
ns1-7.akam.net (2600:1401:2::7)30
usc1.akam.net (95.100.168.64)30
usc2.akam.net (184.26.160.64)30
use4.akam.net (23.211.133.65)30

Checks

  • ✓ Serial 30 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    expire 3d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 6h, retry 1h, expire 3d, negative TTL 5m.
    #23
  • i
    Hidden master
    The primary nameserver ns-cloud-e1.googledomains.com 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 cloud-dns-hostmaster@google.com #25
    The SOA RNAME cloud-dns-hostmaster.google.com means cloud-dns-hostmaster@google.com.
  • ✓ Counter serial #26
    The serial 30 is a plain counter.

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

12 records at the apex

Found

Read from
2.16.130.64:53
TypeValueTTL
SOAns-cloud-e1.googledomains.com. cloud-dns-hostmaster.google.com. 30 21600 3600 259200 30021600
NSuse4.akam.net.300
NSns1-22.akam.net.300
NSeur1.akam.net.300
NSusc2.akam.net.300
NSusc1.akam.net.300
NSeur3.akam.net.300
NSeur4.akam.net.300
NSns1-7.akam.net.300
A88.221.168.83300
MX10 mail.marriott.com.300
TXT"facebook-domain-verification=gcrs9fw3moaaglxprubkfd1ne9apse"300

Checks

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