Skip to content
https://sonypictures.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.sonypictures.com/
200https://sonypictures.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://sonypictures.com/ https://sonypictures.com/

Consistent

B
TLS Certificate Expiry & Recommendations
155 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 14 ms lookup
PASS
1 A records, 14 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 184.24.20.81
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:c900:487::151a, 2a02:26f0:c900:483::151a
Info::
8 nameserver(s) configured
Got: ns16.ultradns2.com, ns16.ultradns2.org, pdns71.ultradns.co.uk, pdns71.ultradns.biz, pdns71.ultradns.com, pdns71.ultradns.net, pdns71.ultradns.org, pdns71.ultradns.info
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: 14 ms
Got: 14 ms
A184.24.20.81
AAAA2a02:26f0:c900:487::151a, 2a02:26f0:c900:483::151a
CNAME
NSns16.ultradns2.com, ns16.ultradns2.org, pdns71.ultradns.co.uk, pdns71.ultradns.biz, pdns71.ultradns.com, pdns71.ultradns.net, pdns71.ultradns.org, pdns71.ultradns.info
MX
10 mxb-009db701.gslb.pphosted.com
10 mxa-009db701.gslb.pphosted.com
TXT
MS=ms97245867
_p9qxz7ipay9ptzx2xhdsaaeoe4y4uoe
SFMC-vLu7pvhTNkV7Ej4Xrl-J69gxg52sM8CJuDgfdko_
openai-domain-verification=dv-SkB7cnA1eTjvrRgXth1ML3CK
facebook-domain-verification=peo1j4efb4p5ya9rgm1idth9lnyxhc
facebook-domain-verification=ycqy1mtilrjmmfpnmwdslhhk0c30qw
yahoo-verification-key=aJj1CSOhwh9NmPClmYq3VVI3AX1n1Og4YOvcnkcxOhE=
google-site-verification=6MpWbMybFZ3AyAoKCWtT4uhjyDQ7gc8CbXLHzFZBBtI
google-site-verification=0AO0_ihFtOOG1jbTcD0yC_00gsKFu9cNTDvt8SjRfg4
MS=ms72815606 adobe-idp-site-verification=15936019-9567-418b-96f8-d1ddd7645dce
SPF v=spf1 include:spf.protection.outlook.com include:cust-spf.exacttarget.com inclu...
CAALookup not available with standard resolver
Resolved in 14 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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), 39 ms total
PASS
1 redirect(s), 39 ms total
Info::
Single redirect
Got: https://sonypictures.com → https://www.sonypictures.com/ (301)
Info::
WWW normalization redirect

https://sonypictures.com

14 ms · HTTP/1.1

301

https://www.sonypictures.com/

25 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sonypictures.com30114 msHTTP/1.1AkamaiGHost
2https://www.sonypictures.com/20025 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:c900:487::151a, 2a02:26f0:c900:483::151a
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:c900:487::151a, 2a02:26f0:c900:483::151a Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 1586 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 1586 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout

A+
Domain Intelligence
sonypictures.com — via MarkMonitor Inc., 29 years, 5 months old
PASS
sonypictures.com — via MarkMonitor Inc., 29 years, 5 months old
Info::
Domain registered until Apr 3, 2027 (11 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: MarkMonitor 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.
Domain expiry

261 days

April 3, 2027

SSL certificate

155 days

Issued by DigiCert Inc

Domain age

29 years, 5 months

Registered April 2, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:c900:487::151a

Registrar

MarkMonitor Inc.

Unlocked 6 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 MarkMonitor Inc.
Created April 2, 1997 (29 years, 5 months ago)
Expires April 3, 2027 (11 months)
Last Updated March 2, 2026
Name Servers pdns71.ultradns.biz, pdns71.ultradns.co.uk, pdns71.ultradns.com, pdns71.ultradns.info, pdns71.ultradns.net, pdns71.ultradns.org
DNSSEC Not enabled
Hosting
IP Address 2a02:26f0:c900:487::151a
Data source: rdap (0.1s)

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 10 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
11 ms
Total Time Total request time from DNS lookup through full response.
11 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 2 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