www.jp.playstation.com

Zone jp.playstation.com · Checked 22 October 2026, 11:34 UTC · via 8.8.8.8
!Passed with warnings
24 passed 4 warnings 0 failed 3 info

Registration

warn

.com generic · 1API GmbH · expires 2027-01-13

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
1API GmbH
Registered
14 January 1997
Last changed
22 November 2025
Expires
13 January 2027
Status
client transfer prohibited
Registry nameservers
ns-1039.awsdns-01.org, ns-1962.awsdns-53.co.uk, ns-43.awsdns-05.com, ns-957.awsdns-55.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-01-13 #3
    The registration is valid until 2027-01-13 (82 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • !
    Registry and delegation differ
    Only at the registry: ns-1039.awsdns-01.org, ns-1962.awsdns-53.co.uk, ns-43.awsdns-05.com, ns-957.awsdns-55.net; only in the parent zone: a1-22.akam.net, a12-65.akam.net, a13-66.akam.net, a2-67.akam.net, a24-64.akam.net, a3-65.akam.net. The registry database and the published delegation should be identical; a pending change may not have been published yet.
    #5

Delegation

info

a1-22.akam.net, a12-65.akam.net, a13-66.akam.net, a2-67.akam.net, a24-64.akam.net, a3-65.akam.net

Found

Parent zone
playstation.com
Delegation from
ns-1039.awsdns-01.org (205.251.196.15)
NS at the parent
a1-22.akam.net, a12-65.akam.net, a13-66.akam.net, a2-67.akam.net, a24-64.akam.net, a3-65.akam.net
NS in the zone
a1-22.akam.net, a12-65.akam.net, a13-66.akam.net, a2-67.akam.net, a24-64.akam.net, a3-65.akam.net
NameserverAddressesNetwork (AS)Glue
a1-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-
a12-65.akam.net184.26.160.65 2600:1480:f000::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a13-66.akam.net2.22.230.66 2600:1480:800::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a2-67.akam.net95.100.174.67 2600:1480:7000::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a24-64.akam.net2.16.130.64 2600:1480:9800::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a3-65.akam.net96.7.49.65 2600:1408:1c::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-22.akam.net, a12-65.akam.net, a13-66.akam.net, a2-67.akam.net, a24-64.akam.net, a3-65.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 6 IPv4 /24s and 6 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): 11 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-22.akam.net 193.108.91.22NOERROR, 3 ms, authoritativenoyes / yesrefused41824.11
a1-22.akam.net 2600:1401:2::16NOERROR, 4 ms, authoritativenoyes / yesrefused41824.10
a12-65.akam.net 184.26.160.65NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
a12-65.akam.net 2600:1480:f000::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.31
a13-66.akam.net 2.22.230.66NOERROR, 4 ms, authoritativenoyes / yesrefused41824.6
a13-66.akam.net 2600:1480:800::42NOERROR, 3 ms, authoritativenoyes / yesrefused41824.4
a2-67.akam.net 95.100.174.67NOERROR, 5 ms, authoritativenoyes / yesrefused48878.27
a2-67.akam.net 2600:1480:7000::43NOERROR, 4 ms, authoritativenoyes / yesrefused48878.27
a24-64.akam.net 2.16.130.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.33
a24-64.akam.net 2600:1480:9800::40NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
a3-65.akam.net 96.7.49.65NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11
a3-65.akam.net 2600:1408:1c::41NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11

Checks

  • ✓ All respond #14
    All 12 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: a1-22.akam.net: "41824.11"; a1-22.akam.net: "41824.10"; a12-65.akam.net: "48878.32"; a12-65.akam.net: "48878.31"; a13-66.akam.net: "41824.6"; a13-66.akam.net: "41824.4"; a2-67.akam.net: "48878.27"; a24-64.akam.net: "48878.33"; a24-64.akam.net: "48878.29"; a3-65.akam.net: "41824.11". 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

pass

serial 1552630111 · primary a3-65.akam.net

Found

Primary (MNAME)
a3-65.akam.net
Contact (RNAME)
hostmaster.akamai.com
Serial
1552630111
Refresh / retry
43200 s / 7200 s
Expire
604800 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
a1-22.akam.net (193.108.91.22)1552630111
a1-22.akam.net (2600:1401:2::16)1552630111
a12-65.akam.net (184.26.160.65)1552630111
a12-65.akam.net (2600:1480:f000::41)1552630111
a13-66.akam.net (2.22.230.66)1552630111
a13-66.akam.net (2600:1480:800::42)1552630111
a2-67.akam.net (95.100.174.67)1552630111
a2-67.akam.net (2600:1480:7000::43)1552630111
a24-64.akam.net (2.16.130.64)1552630111
a24-64.akam.net (2600:1480:9800::40)1552630111
a3-65.akam.net (96.7.49.65)1552630111
a3-65.akam.net (2600:1408:1c::41)1552630111

Checks

  • ✓ Serial 1552630111 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 7d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a3-65.akam.net is one of the listed nameservers.
  • ✓ Contact hostmaster@akamai.com #25
    The SOA RNAME hostmaster.akamai.com means hostmaster@akamai.com.
  • ✓ Timestamp serial #26
    The serial 1552630111 is a Unix timestamp (2019-03-15 06:08 UTC).

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

46 records at the apex

Found

Read from
193.108.91.22:53
TypeValueTTL
SOAa3-65.akam.net. hostmaster.akamai.com. 1552630111 43200 7200 604800 720086400
NSa13-66.akam.net.172800
NSa1-22.akam.net.172800
NSa2-67.akam.net.172800
NSa24-64.akam.net.172800
NSa3-65.akam.net.172800
NSa12-65.akam.net.172800
A2.16.183.2020
A2.16.183.2420
MX20 mail02.scej-nbs.jp.3600
MX10 mail01.scej-nbs.jp.3600
TXT"00DWG0000048OkV=1TBWG0000000M8b"3600
TXT"00DWF000006yay1=1TBWF0000000Z0z"3600
TXT"\"facebook-domain-verification=wz3mpvoze6vwvny5jp7jcvpw4jfqkj\""3600
TXT"v=spf1 +ip4:13.114.90.221/32 +ip4:18.177.193.151/32 +ip4:13.114.90.221/32 +ip4:52.69.136.237/32 +ip4:52.194.116.184/32 +ip4:18.179.130.85/32 +ip4:54.92.77.49 +ip4:18.177.193.151/32 +ip4:202.130.63.23/32 +ip4:124.109.181.7/32 +ip4:219.106.250.246/32 " " +ip4:54.249.199.1/32 +ip4:54.95.20.210 +ip4:13.114.154.84 +ip4:13.230.70.193 " "include:rnmk.com mx include:_spf.salesforce.com include:spf.makeshop.jp ~all"3600
TXT"00DWF000005oadJ=1TBWF0000000UKf"3600
TXT"00D55000000AU1R=1TBWF0000000PPp"3600
TXT"00D6C00000010N1=1TBWF0000000S2j"3600
TXT"00DWG000002XHIf=1TBWG0000000Ihh"3600
TXT"00DWF00000BLrsb=1TBWF0000000LCX"3600
TXT"00DWF000006X7Qf=1TBWF0000000QaQ"3600
TXT"00DWe000001Yqmn=1TBWe0000000DbZ"3600
TXT"00DWG000003GQ0F=1TBWG0000000JsH"3600
TXT"00D100000004iyF=1TBfP00000002hl"3600
TXT"00DWG000004ARsf=1TBWG0000000F8j"3600
TXT"00Ddl000004Jkw5=1TBdl0000000ZU1"3600
TXT"00DWF00000BLrcT=1TBWF0000000XqP"3600
TXT"00DO00000000hB3=1TBA800000006On"3600
TXT"00DP0000000Gvsm=1TBWF0000000QQj"3600
TXT"00Ddh000000n7A1=1TBdh0000000MLV"3600
TXT"00DWG000004FIjt=1TBWG0000000HP3"3600
TXT"00DWG00000191fR=1TBWG0000000KtC"3600
TXT"00DWK000003CdyL=1TBWK0000000Cyr"3600
TXT"google-site-verification=BPEJfX32tlrgfqC1dJ-AFP0smyuy__wWxrnT2Y39CoY"3600
TXT"00DWG0000034J2L=1TBWG0000000NEL"3600
TXT"00Ddn000002K0HF=1TBdn00000007RJ"3600
TXT"00DWF0000081Ulp=1TBWF0000000Mrl"3600
TXT"00DWF000004plvW=1TBWF0000000VVF"3600
TXT"00DWF00000BLrhJ=1TBWF0000000Wfp"3600
TXT"00D3J0000008lPt=1TBWF00000007He"3600
TXT"00DWG000003GOFx=1TBWG0000000GBF"3600
TXT"00Ddq000005tB6P=1TBdq0000000S4L"3600
TXT"00D2i0000008eKi=1TBWF0000000OFF"3600
TXT"00DV9000003xfIL=1TBV90000000DlF"3600
TXT"00DWF000004xt9R=1TBWF0000000T8T"3600
TXT"00D3h00000669Bv=1TBa600000002LJ"3600

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