Skip to content
https://pokemon.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
4 PASS 3 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.pokemon.com/
200https://pokemon.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://pokemon.com/ http://www.pokemon.com/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 1039 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1039 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<html style="height:100%"><head><META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"><meta name="format-detection" content="telephone=no"><meta name="viewport" content="initial-scale=1.0"><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"><script type="text/javascript" src="/_Incapsula_Resource?SWJIYLWA=719d34d31c8e3a6e6fffd425f7e032f3"></script><script src="/d-Headiction-our-How-and-ther-Lord-That-manly-sp" async></script></head><body style="margin:0px;height:100%"><iframe id="main-iframe" src="/_Incapsula_Resource?SWUDNSAI=31&xinfo=12-21894539-0%20SNNN%20RT%281776894410338%20316%29%20q%280%20-1%20-1%200%29%20r%280%20-1%29%20B12%2814%2c0%2c0%29%20U24&incident_id=1396000630073226674-109483952031666124&edet=12&cinfo=0e0000000e6f&rpinfo=0&cts=oCqArE35fKRxIh%2bLkkHFkH5eMPyzYAo9XrLHfFgHRBhycjmk7uriZYk%2fuq7MG0Me&cip=141.227.188.119&mth=GET" frameborder=0 width="100%" height="100%" marginheight="0px" marginwidth="0px">Request unsuccessful. Incapsula incident ID: 1396000630073226674-109483952031666124</iframe></body></html>
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
168 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

168
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
2 A records, 131 ms lookup
PASS
2 A records, 131 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 34.198.240.233, 52.54.23.246
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1710.awsdns-21.co.uk, ns-677.awsdns-20.net, ns-1264.awsdns-30.org, ns-324.awsdns-40.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 131 ms
Got: 131 ms
A34.198.240.233, 52.54.23.246
AAAA
CNAME
NSns-1710.awsdns-21.co.uk, ns-677.awsdns-20.net, ns-1264.awsdns-30.org, ns-324.awsdns-40.com
MX
10 us-smtp-inbound-2.mimecast.com
10 us-smtp-inbound-1.mimecast.com
TXT
adobe-idp-site-verification=f797494c-717a-46d1-aedf-8a2016497c76
globalsign-domain-verification=6806CF5E02E0303340D643B8EDDA3436
abd11ec54f
atlassian-domain-verification=oCtdU8ImpwPyWbxOnS6fTVhkygfI8Wj14911qO1VUm2Pm9d0kP...
airtable-verification=7898b9e18e78e5f4673f94ed7a2e0502
docker-verification=6c629d3c-1c0d-46bb-a7b9-9cb4febff587
v=1;k=zia;b=test;t=1770223947;n=2;p=2;bh=3f8YuKXwLxk6iurXHwBzirOxSVTxYPkP1kZMRZ9...
postman-domain-verification=bfb789bae8ef37237c45946574177389d0fb50b463a40a4336fd...
SPF v=spf1 include:us._netblocks.mimecast.com include:mailgun.org include:mail.zend...
datadome-domain-verify=OTtSW3LgYkP9aowkrlRkkHRy0kfOKFhj
globalsign-domain-verification=8BBE28844237508DEB7124E866F43363
neat-pulse-domain-verification-BwNQrlv=455e45c6-70b9-4a9a-82ea-85b9d3db5807
V_N5aMmKb67VXhl32PcebtIiIQ
parallels-domain-verification=4f3a39eafa144cee8cafeb5fd987695bd587286716454d0a82...
google-site-verification=kMrlFcdelRSLEGNoUJFosllCY82lhgxXd8X4WhLBJNo
_uuimtut5rbcfxalia2sgwiwndk7qw5z
monday-com-verification=HYPbj4ORdm7hYwd9630jWGXL8V_a_7ugyamylA9exJ0
google-site-verification=LD3TFbLy2frzXDC0k6DkeeVrY41PKQuIOL-0Waouric
jamf-site-verification=kY7ydKmQ5a-6tIc7zkHpuQ
have-i-been-pwned-verification=8c64dcff6f191e2216f09fda318b9185
anthropic-domain-verification-axcxsw=NyuWWIqrSUAYL867CpPliCWM3
v=1;k=zia;b=test;t=1770223947;n=2;p=1;bh=QY9xlphVBEos4hKlMqp/FnP57kydQM98SmsP/uU...
MS=ms54518632
smartsheet-site-validation=eOYAS-maaFRJlq1t5letAmPT-BLGiifM
autodesk-domain-verification=LWkQRRoiBN3g87HOZJ4n
amazonses:2GSi526ZBbSguTOe9sm7cMzzsCFDAwR2+mGtCfw91I0=
miro-verification=7a5c2783d3e4cae1bde6d4f1a5c65379ef413968
globalsign-domain-verification=92469096885399DE4E17310AC996B162
canva-site-verification=i5yp2RvoW9CvAuKzDsBopQ
duo_sso_verification=vvQUm4vhB1SOrsEf2q6rHMyqQqF7lLm3EI4sh8VP8jcMdk1sQa8lLrl9Zlw...
slack-domain-verification=8etIUWyeNMpfqH9ybMRVoHQTKMQiGJc1hqTJWCsc
box-domain-verification=33fa48b02cc084a69046284135bc05cde4269ed241c96d53616c53db...
wrike-verification=NTI3MzU5ODo4YjU4M2EzYWE2YmZjNDY4NzMzOWUwYTAzZTNhZGQ4ODJhNGZhY...
google-site-verification=AJ9ZT5WkA-2UjRIQsl5ob5FFMkaT0k9r80b169J8qT8
lf7hRJtYi+KWSWBPonouSXTE5OW2JvS/rZZHcNPivd/IenFoWqKFSpHPevEYzqUTVzKAnJ3gHzdzCEMc...
apple-domain-verification=LxNZz52i0yminHcB
globalsign-domain-verification=F80650FD160271784BCA946F097B14A2
paloaltonetworks-site-verification=ea989be1d68a41fb340398684d9233ab4594a90d97145...
amazonses:q1XMEc94NM9woXRvxlOCxCMMMNMBFpN4ZRc7BgIhHyg=
CAALookup not available with standard resolver
Resolved in 131 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 511 ms total
PASS
1 redirect(s), 511 ms total
Info::
Single redirect
Got: https://pokemon.com → http://www.pokemon.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://pokemon.com
Info::
Redirect overhead: 511 ms total
Got: 511 ms

https://pokemon.com

387 ms · HTTP/1.1

302

http://www.pokemon.com/

124 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pokemon.com302387 msHTTP/1.1Apache/2.4.58 (Unix) OpenSSL/3.1.4
2http://www.pokemon.com/200124 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Domain Intelligence
pokemon.com — via CSC Corporate Domains, Inc., 28 years, 8 months old, hosted on AWS
PASS
pokemon.com — via CSC Corporate Domains, Inc., 28 years, 8 months old, hosted on AWS
Info::
Domain registered until Jan 7, 2028 (1 years, 8 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

572 days

January 7, 2028

SSL certificate

168 days

Issued by Amazon

Domain age

28 years, 8 months

Registered January 8, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.54.23.246

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created January 8, 1998 (28 years, 8 months ago)
Expires January 7, 2028 (1 years, 8 months)
Last Updated January 3, 2026
Name Servers ns-1264.awsdns-30.org, ns-1710.awsdns-21.co.uk, ns-324.awsdns-40.com, ns-677.awsdns-20.net
DNSSEC Not enabled
Hosting
IP Address 52.54.23.246
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 465 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
52 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
102 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
206 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
466 ms
Total Time Total request time from DNS lookup through full response.
466 ms

Connection waterfall

DNS Lookup 52 ms TCP Connect 102 ms TLS Handshake 206 ms Server Processing 106 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback