shangri-la.com

Checked 22 October 2026, 10:41 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 6 info

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-05-04

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
3 May 1995
Last changed
30 April 2026
Expires
4 May 2027
Status
client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
eur2.akam.net, eur4.akam.net, eur5.akam.net, eur6.akam.net, ns1-137.akam.net, ns1-171.akam.net, use2.akam.net, use3.akam.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-05-04 #3
    The registration is valid until 2027-05-04 (193 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

eur2.akam.net, eur4.akam.net, eur5.akam.net, eur6.akam.net, ns1-137.akam.net, ns1-171.akam.net, use2.akam.net, use3.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
eur2.akam.net, eur4.akam.net, eur5.akam.net, eur6.akam.net, ns1-137.akam.net, ns1-171.akam.net, use2.akam.net, use3.akam.net
NS in the zone
eur2.akam.net, eur4.akam.net, eur5.akam.net, eur6.akam.net, ns1-137.akam.net, ns1-171.akam.net, use2.akam.net, use3.akam.net
NameserverAddressesNetwork (AS)Glue
eur2.akam.net95.100.173.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur4.akam.net84.53.139.64AS20940 AKAMAI-ASN1 - Akamai International B.V., NL-
eur5.akam.net23.74.25.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur6.akam.net2.22.230.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-137.akam.net193.108.91.137 2600:1401:2::89AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-171.akam.net193.108.91.171 2600:1401:2::abAS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use2.akam.net96.7.49.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use3.akam.net96.7.49.65AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 8 nameservers #6
    Delegated to eur2.akam.net, eur4.akam.net, eur5.akam.net, eur6.akam.net, ns1-137.akam.net, ns1-171.akam.net, use2.akam.net, use3.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): 2 addresses; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 8 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: eur2.akam.net, eur4.akam.net, eur5.akam.net, eur6.akam.net, use2.akam.net, use3.akam.net.
    #13

Nameservers

warn

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
eur2.akam.net 95.100.173.64NOERROR, 4 ms, authoritativenoyes / yesrefused48878.27
eur4.akam.net 84.53.139.64NOERROR, 7 ms, authoritativenoyes / yesrefused41824.10
eur5.akam.net 23.74.25.64NOERROR, 4 ms, authoritativenoyes / yesrefused48878.27
eur6.akam.net 2.22.230.64NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11
ns1-137.akam.net 193.108.91.137NOERROR, 3 ms, authoritativenoyes / yesrefused41824.6
ns1-137.akam.net 2600:1401:2::89NOERROR, 4 ms, authoritativenoyes / yesrefused41824.8
ns1-171.akam.net 193.108.91.171NOERROR, 4 ms, authoritativenoyes / yesrefused41824.4
ns1-171.akam.net 2600:1401:2::abNOERROR, 4 ms, authoritativenoyes / yesrefused41824.10
use2.akam.net 96.7.49.64NOERROR, 4 ms, authoritativenoyes / yesrefused41824.9
use3.akam.net 96.7.49.65NOERROR, 4 ms, authoritativenoyes / yesrefused41824.7

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: eur2.akam.net: "48878.27"; eur4.akam.net: "41824.10"; eur5.akam.net: "48878.27"; eur6.akam.net: "41824.11"; ns1-137.akam.net: "41824.6"; ns1-137.akam.net: "41824.8"; ns1-171.akam.net: "41824.4"; ns1-171.akam.net: "41824.10"; use2.akam.net: "41824.9"; use3.akam.net: "41824.7". 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 2019101471 · primary b1.uberns.com

Found

Primary (MNAME)
b1.uberns.com
Contact (RNAME)
tio.team.shangri-la.com
Serial
2019101471
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
eur2.akam.net (95.100.173.64)2019101471
eur4.akam.net (84.53.139.64)2019101471
eur5.akam.net (23.74.25.64)2019101471
eur6.akam.net (2.22.230.64)2019101471
ns1-137.akam.net (193.108.91.137)2019101471
ns1-137.akam.net (2600:1401:2::89)2019101471
ns1-171.akam.net (193.108.91.171)2019101471
ns1-171.akam.net (2600:1401:2::ab)2019101471
use2.akam.net (96.7.49.64)2019101471
use3.akam.net (96.7.49.65)2019101471

Checks

  • ✓ Serial 2019101471 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • i
    Hidden master
    The primary nameserver b1.uberns.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 tio@team.shangri-la.com #25
    The SOA RNAME tio.team.shangri-la.com means tio@team.shangri-la.com.
  • ✓ Date-based serial #26
    The serial 2019101471 follows the YYYYMMDDnn convention (2019-10-14).

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

29 records at the apex

Found

Read from
95.100.173.64:53
TypeValueTTL
SOAb1.uberns.com. tio.team.shangri-la.com. 2019101471 10800 3600 604800 36003600
NSeur6.akam.net.3600
NSns1-171.akam.net.3600
NSuse3.akam.net.3600
NSeur4.akam.net.3600
NSuse2.akam.net.3600
NSns1-137.akam.net.3600
NSeur5.akam.net.3600
NSeur2.akam.net.3600
A163.181.58.171300
A163.181.58.177300
A163.181.58.173300
A163.181.58.176300
A163.181.58.175300
A163.181.58.172300
A163.181.58.170300
A163.181.58.174300
MX0 shangrila-com01i.mail.protection.outlook.com.3600
TXT"ms-domain-verification=1858d432-660d-4ff1-b21e-f27bf7bccd41"3600
TXT"google-site-verification=bFqhpQOCCvNOwWWbodfzkjo9Q_36O51Y_Fh1-JI1bCk"3600
TXT"facebook-domain-verification=oear91qyuqa62cwg140sx9xmk731r6"3600
TXT"htwyzk88wl0yr674wqwh29mf68nnyvn8"3600
TXT"S7ffwSPCLe09DsIfbRJyJmtSeVZsKWvCrAu+ZWPjDwI="3600
TXT"ZAC91674423"3600
TXT"facebook-domain-verification=l4t8u6deh6d0ka6xcjbidtw53uha9q"3600
TXT"smartsheet-site-validation=DdmeQhR8J7NX5H3Rswp8UQC3REPRNxKj"3600
TXT"facebook-domain-verification=7jffgwg0h16gsr7x8bod600kcau7yg, facebook-domain-verification=02466a5il0pu4dsnv1qmk282fjrdc9"3600
TXT"adobe-idp-site-verification=e0098eb3a3013893ccc93d8b645d762f155406826c9ce325f8c76a6a73d34bc6"3600
TXT"v=spf1 ip4:37.10.0.0/18 include:spf-hotel.shangri-la.com include:spf-vendor.shangri-la.com include:spf02.sabacloud.com include:spf.protection.outlook.com include:_spf.salesforce.com " "include:shops.shopify.com include:_spf-dc10.sapsf.com include:amazonses.com include:spf.zohomail360.com -all"3600

Checks

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