jcpenney.com

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

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-10-12

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
13 October 1993
Last changed
8 October 2026
Expires
12 October 2027
Status
client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
asia3.akam.net, eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-242.akam.net, ns1-8.akam.net, use1.akam.net, use4.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-10-12 #3
    The registration is valid until 2027-10-12 (354 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

asia3.akam.net, eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-242.akam.net, ns1-8.akam.net, use1.akam.net, use4.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
asia3.akam.net, eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-242.akam.net, ns1-8.akam.net, use1.akam.net, use4.akam.net
NS in the zone
asia3.akam.net, eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-242.akam.net, ns1-8.akam.net, use1.akam.net, use4.akam.net
NameserverAddressesNetwork (AS)Glue
asia3.akam.net23.211.61.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur2.akam.net95.100.173.64AS21342 AKAMAI-ASN2 - 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-242.akam.net193.108.91.242 2600:1401:2::f2AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-8.akam.net193.108.91.8 2600:1401:2::8AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use1.akam.net72.246.46.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 asia3.akam.net, eur2.akam.net, eur5.akam.net, eur6.akam.net, ns1-242.akam.net, ns1-8.akam.net, use1.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: asia3.akam.net, eur2.akam.net, eur5.akam.net, eur6.akam.net, use1.akam.net, use4.akam.net.
    #13

Nameservers

warn

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
asia3.akam.net 23.211.61.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
eur2.akam.net 95.100.173.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
eur5.akam.net 23.74.25.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.29
eur6.akam.net 2.22.230.64NOERROR, 3 ms, authoritativenoyes / yesrefused41824.8
ns1-242.akam.net 193.108.91.242NOERROR, 4 ms, authoritativenoyes / yesrefused41824.9
ns1-242.akam.net 2600:1401:2::f2NOERROR, 3 ms, authoritativenoyes / yesrefused41824.7
ns1-8.akam.net 193.108.91.8NOERROR, 3 ms, authoritativenoyes / yesrefused41824.7
ns1-8.akam.net 2600:1401:2::8NOERROR, 7 ms, authoritativenoyes / yesrefused41824.7
use1.akam.net 72.246.46.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.29
use4.akam.net 23.211.133.65NOERROR, 3 ms, authoritativenoyes / yesrefused48878.27

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: asia3.akam.net: "48878.32"; eur2.akam.net: "48878.26"; eur5.akam.net: "48878.29"; eur6.akam.net: "41824.8"; ns1-242.akam.net: "41824.9"; ns1-242.akam.net: "41824.7"; ns1-8.akam.net: "41824.7"; use1.akam.net: "48878.29"; use4.akam.net: "48878.27". 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 2015101519 · primary a1-235.akam.net

Found

Primary (MNAME)
a1-235.akam.net
Contact (RNAME)
techadmin.jcpenney.com
Serial
2015101519
Refresh / retry
300 s / 300 s
Expire
300 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
asia3.akam.net (23.211.61.64)2015101519
eur2.akam.net (95.100.173.64)2015101519
eur5.akam.net (23.74.25.64)2015101519
eur6.akam.net (2.22.230.64)2015101519
ns1-242.akam.net (193.108.91.242)2015101519
ns1-242.akam.net (2600:1401:2::f2)2015101519
ns1-8.akam.net (193.108.91.8)2015101519
ns1-8.akam.net (2600:1401:2::8)2015101519
use1.akam.net (72.246.46.64)2015101519
use4.akam.net (23.211.133.65)2015101519

Checks

  • ✓ Serial 2015101519 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m; expire 5m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 5m must be longer than refresh + retry. Current values: refresh 5m, retry 5m, expire 5m, negative TTL 5m.
    #23
  • i
    Hidden master
    The primary nameserver a1-235.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 techadmin@jcpenney.com #25
    The SOA RNAME techadmin.jcpenney.com means techadmin@jcpenney.com.
  • ✓ Date-based serial #26
    The serial 2015101519 follows the YYYYMMDDnn convention (2015-10-15).

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

33 records at the apex

Found

Read from
23.211.61.64:53
TypeValueTTL
SOAa1-235.akam.net. techadmin.jcpenney.com. 2015101519 300 300 300 300300
NSuse4.akam.net.300
NSns1-8.akam.net.300
NSeur6.akam.net.300
NSns1-242.akam.net.300
NSeur5.akam.net.300
NSasia3.akam.net.300
NSuse1.akam.net.300
NSeur2.akam.net.300
A23.67.142.1920
MX10 jcpenney-com.mail.protection.outlook.com.120
TXT"google-site-verification=tlhWUTTrJYEjqAYeBRDpCd4zxRCkbPmrmsjNKNOhUs4"120
TXT"_q0dpkydxbnd2om8lokpe2xdh3piss90"120
TXT"asv_domain=737d778734f3c9e3bb09d87e8bb09499"120
TXT"onetrust-domain-verification=2806f764d326484d81e2301ac82d3875"120
TXT"figma-domain-verification=875edfb439bab32d871ed073e975333233f67f68a460cc949917dc1a61ea770e-1756303824"120
TXT"_9aj8ftgjux6fh4lm3h9qzv340zumz8v"120
TXT"ARh+0bkmjsHjGceqXF9FxepJEXiWdBkbChZuHWKC3wWc78qCIjsi/3QVP7zu4zGeHcX3cxxKO5HkdYXB3npxuQ=="120
TXT"figma-domain-verification=70850040bcb8d1f118707f542b36cefa1a81ddc66cd2c7d8000dae4b763f14b4-1757369053"120
TXT"_a7ci0ynrmwha49ab17tsm9d5evb9edy"120
TXT"atlassian-domain-verification=n2UiS9Mnk0ciaRfDoqZ7E7mDp4hUdFa0ZXxpUPObRHgYkkT0zD2Yu/HbE0t84b1C"120
TXT"_rj2dap2vayat1k59ixhlvp03ku4ohgx"120
TXT"_ewmez3r3m1ozvcyc1twfxgxmjw013u0"120
TXT"MS=ms92767715"120
TXT"figma-domain-verification=da68225c3b03c43e5d326702f3f1e0a2ba9ced7000952dc9723dc62756d6c0d0-1757617199"120
TXT"_c4xutk98d8drd1ghuwvqhx6p81skt8p"120
TXT"_x4hm91p3l4steb55hfq54ugf2rbjpf4"120
TXT"v=spf1 include:spf01.jcp.com include:spf.protection.outlook.com -all"120
TXT"figma-domain-verification=7ae0277a900bc89be6d3c1abedeed9a34f8dbc9270cff7cacd282db865133c9d-1757987848"120
TXT"figma-domain-verification=43e962ed0d2b6f0faa9faf07764486e49f3bc6ea3644f497dc0689b100533264-1757952191"120
TXT"_cmytxs4ym28e1j1b88u37mbmhvf7qoj"120
TXT"adobe-idp-site-verification=3ca6e8ad-9051-45ac-8f87-0cd27ae78897"120
TXT"_mtds4l2xvgse0dpb9hdp5j6cdnzol0n"120

Checks

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