princess.com

Checked 22 October 2026, 10:21 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 5 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2026-12-09

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
10 December 1998
Last changed
7 November 2025
Expires
9 December 2026
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
asia2.akam.net, eur6.akam.net, ns1-136.akam.net, ns1-208.akam.net, usc4.akam.net, use9.akam.net, usw1.akam.net, usw4.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 2026-12-09 #3
    The registration is valid until 2026-12-09 (47 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

asia2.akam.net, eur6.akam.net, ns1-136.akam.net, ns1-208.akam.net, usc4.akam.net, use9.akam.net, usw1.akam.net, usw4.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
asia2.akam.net, eur6.akam.net, ns1-136.akam.net, ns1-208.akam.net, usc4.akam.net, use9.akam.net, usw1.akam.net, usw4.akam.net
NS in the zone
asia2.akam.net, eur6.akam.net, ns1-136.akam.net, ns1-208.akam.net, usc4.akam.net, use9.akam.net, usw1.akam.net, usw4.akam.net
NameserverAddressesNetwork (AS)Glue
asia2.akam.net95.101.36.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur6.akam.net2.22.230.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-136.akam.net193.108.91.136 2600:1401:2::88AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-208.akam.net193.108.91.208 2600:1401:2::d0AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usc4.akam.net184.26.160.65AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use9.akam.net72.246.46.65AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usw1.akam.net23.61.199.66AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usw4.akam.net184.26.161.65 2600:1480:1800::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 8 nameservers #6
    Delegated to asia2.akam.net, eur6.akam.net, ns1-136.akam.net, ns1-208.akam.net, usc4.akam.net, use9.akam.net, usw1.akam.net, usw4.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 7 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 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): 10 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: asia2.akam.net, eur6.akam.net, usc4.akam.net, use9.akam.net, usw1.akam.net.
    #13

Nameservers

warn

11 of 11 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
asia2.akam.net 95.101.36.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.30
eur6.akam.net 2.22.230.64NOERROR, 5 ms, authoritativenoyes / yesrefused41824.8
ns1-136.akam.net 193.108.91.136NOERROR, 4 ms, authoritativenoyes / yesrefused41824.9
ns1-136.akam.net 2600:1401:2::88NOERROR, 4 ms, authoritativenoyes / yesrefused41824.5
ns1-208.akam.net 193.108.91.208NOERROR, 3 ms, authoritativenoyes / yesrefused41824.7
ns1-208.akam.net 2600:1401:2::d0NOERROR, 5 ms, authoritativenoyes / yesrefused41824.11
usc4.akam.net 184.26.160.65NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
use9.akam.net 72.246.46.65NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
usw1.akam.net 23.61.199.66NOERROR, 4 ms, authoritativenoyes / yesrefused41824.10
usw4.akam.net 184.26.161.65NOERROR, 5 ms, authoritativenoyes / yesrefused48878.33
usw4.akam.net 2600:1480:1800::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31

Checks

  • ✓ All respond #14
    All 11 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: asia2.akam.net: "48878.30"; eur6.akam.net: "41824.8"; ns1-136.akam.net: "41824.9"; ns1-136.akam.net: "41824.5"; ns1-208.akam.net: "41824.7"; ns1-208.akam.net: "41824.11"; usc4.akam.net: "48878.31"; use9.akam.net: "48878.26"; usw1.akam.net: "41824.10"; usw4.akam.net: "48878.33"; usw4.akam.net: "48878.31". 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 2024040475 · primary princess.com

Found

Primary (MNAME)
princess.com
Contact (RNAME)
domains.princess.com
Serial
2024040475
Refresh / retry
7200 s / 1200 s
Expire
604800 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
asia2.akam.net (95.101.36.64)2024040475
eur6.akam.net (2.22.230.64)2024040475
ns1-136.akam.net (193.108.91.136)2024040475
ns1-136.akam.net (2600:1401:2::88)2024040475
ns1-208.akam.net (193.108.91.208)2024040475
ns1-208.akam.net (2600:1401:2::d0)2024040475
usc4.akam.net (184.26.160.65)2024040475
use9.akam.net (72.246.46.65)2024040475
usw1.akam.net (23.61.199.66)2024040475
usw4.akam.net (184.26.161.65)2024040475
usw4.akam.net (2600:1480:1800::41)2024040475

Checks

  • ✓ Serial 2024040475 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 20m, expire 7d, negative TTL 2h.
  • i
    Hidden master
    The primary nameserver princess.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 domains@princess.com #25
    The SOA RNAME domains.princess.com means domains@princess.com.
  • ✓ Date-based serial #26
    The serial 2024040475 follows the YYYYMMDDnn convention (2024-04-04).

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

21 records at the apex

Found

Read from
95.101.36.64:53
TypeValueTTL
SOAprincess.com. domains.princess.com. 2024040475 7200 1200 604800 72007200
NSns1-208.akam.net.7200
NSusw4.akam.net.7200
NSasia2.akam.net.7200
NSuse9.akam.net.7200
NSeur6.akam.net.7200
NSns1-136.akam.net.7200
NSusc4.akam.net.7200
NSusw1.akam.net.7200
A23.201.252.4920
MX20 mail3.princess.com.7200
MX20 mail4.princess.com.7200
MX10 carnival-com.mail.protection.outlook.com.7200
TXT"mMQ5O/EO3cz7AwkgnO9tHKVXD8e2fKOvBWL9kzEvLSrSX2sA377sOoBTceG1WAyyBg/BW8AWxT7+md+I7Wccew=="60
TXT"knowbe4-site-verification=87f853c8a6ca37a55c53ae74128096d"60
TXT"google-site-verification=HN8PcjJUWyXbAN73m22wtBm6Nlk3tKkCjF3Fam4SCLo"60
TXT"v=spf1 mx include:spf.protection.outlook.com include:spf.sabre.com -all"60
TXT"MS=ms38124960"60
TXT"_mos0p3osi2wew4qka5hj1xx58gtdbi9"60
TXT"ms-domain-verification=e0e21981-40d9-413a-a1eb-e0a09e1b82bf"60
TXT"google-site-verification=ixM2oqt9-U0I3kLeLwSOjQ3GiW8cJi8EVXgx5oHfbQk"60

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 2d and in the zone 2h; 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