Skip to content
https://simonandschuster.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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 503 Expected: 301 redirect to HTTPS

www / non-www

200https://www.simonandschuster.com/
200https://simonandschuster.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

503http://simonandschuster.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

B
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 138 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 references 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

robots.txt 200 OK
Size 138 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow: /external_assets
Disallow: /about/contact_us
Sitemap: https://www.simonandschuster.com/sitemaps/us/sitemap.xml.gz

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
315 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
1 A records, 76 ms lookup
PASS
1 A records, 76 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 44.208.141.18
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns3.p09.nsone.net, dns4.p09.nsone.net, dns1.p09.nsone.net, dns2.p09.nsone.net
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: 76 ms
Got: 76 ms
A44.208.141.18
AAAA
CNAME
NSdns3.p09.nsone.net, dns4.p09.nsone.net, dns1.p09.nsone.net, dns2.p09.nsone.net
MX
10 mxa-0091c601.gslb.pphosted.com
10 mxb-0091c601.gslb.pphosted.com
TXT
docusign=01ef374c-ec82-4ead-b9e3-e511ce785627
MS=ms91182265
adobe-idp-site-verification=c75c1751-8015-46ad-8b19-894bd340d3b7
openai-domain-verification=dv-QmUTuTpDc65Ozd9yOxFyMmXe
MS=ms41218823
specops-verification-code=875ddb67-eaed-4dfb-81e5-a082652573a6
ZOOM_verify_UauGBYryQ0QwE5K1WXHTpg
nl7hmkv2bp1247vpszz8vs19074jmn3y
onetrust-domain-verification=d4905f6c011f4edd9cbf8a10f5b4450d
google-site-verification=irpwSKEMXmVzZbOjxsImNHlGE1dOmPQLOOwAPSvFMUk
jamf-site-verification=V-59GMRXrsCzaAi2eUdOlQ
docusign=0995014e-6bb1-40c0-8357-588909747641
MS=ms82767150
teamviewer-sso-verification=bea78b950a9f4515a86dab58d12b156d
adobe-idp-site-verification=9b12eeee86b1217caefd9bbbc36da8e767b6c0cca5d2d3bf31c4...
atlassian-domain-verification=NX0XJRM8cEb4P5HEYlLZI+xUFM+j6n3Mx6wuVZY/+mMvt5X4/t...
zywave-domain-verification=ikgUqthVQn6KTU8aOw0ZZT1/3CjfvFxuyxMOAAkJw5U=
SPF v=spf1 ip4:192.238.127.32/30 ip4:204.8.104.37 ip4:204.8.106.38 ip4:204.8.106.36 ...
apple-domain-verification=reuBEovZGylS0qgt
facebook-domain-verification=nef2zuu0ohigx7bzjmxvpazfdadvtd
extensis-domain-verification=9b175cf2-adc6-42c3-9a31-b94c595af8e2
google-site-verification=mctqdq1_EPdoZV-BsYQSOJZvgSpXxSV9-Xsde29ejbc
airtable-verification=b1714383409370d45343fc96489b0ba5
A7Yy+d3hgG2WNv6Pj5ORfGJvbaFWntlBhWgww0s5klRnZyW5dkUOknkCG/KUHsxfvsLyIEM9gMeRzt/B...
kmpb/AnWYbCTpM2YXYgP/1x1pWtx6zkt9+9VKmL3jKRUiL4Nv88sOHJP97lLvW4W/xlNPq+ITCwZJ3nI...
yahoo-verification-key=UjXJbhNgfrDnr8Nks59S0zzYGnX2IDW7/LfcMF+pci8=
6F4FFA5F47273F4F57C94E35064CF6AA1BD4966CF1520436367EB0FB79770A1F
appspace-domain-verification=95717daa24b5c09519b505de173a1b8d2d0d37ec64cb70ce7d6...
docusign=9859974c-e575-4bc2-9ae9-8a44666e3d75
_pki-validation.simonandschuster.com
CAALookup not available with standard resolver
Resolved in 76 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), 797 ms total
PASS
1 redirect(s), 797 ms total
Info::
Single redirect
Got: https://simonandschuster.com → https://www.simonandschuster.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 797 ms total
Got: 797 ms

https://simonandschuster.com

297 ms · HTTP/1.1

301

https://www.simonandschuster.com/

500 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://simonandschuster.com301297 msHTTP/1.1nginx
2https://www.simonandschuster.com/200500 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A
Domain Intelligence
simonandschuster.com — via MarkMonitor Inc., 30 years, 4 months old, hosted on AWS
PASS
simonandschuster.com — via MarkMonitor Inc., 30 years, 4 months old, hosted on AWS
Warning::
Domain expires in 35 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 27, 2026
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

EXPIRED

May 27, 2026

SSL certificate

315 days

Issued by Entrust Limited

Domain age

30 years, 4 months

Registered May 28, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

44.208.141.18

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created May 28, 1996 (30 years, 4 months ago)
Expires May 27, 2026 (1 months)
Last Updated April 25, 2025
Name Servers dns1.p09.nsone.net, dns2.p09.nsone.net, dns3.p09.nsone.net, dns4.p09.nsone.net
DNSSEC Not enabled
Hosting
IP Address 44.208.141.18
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 36 ms TCP Connect 97 ms TLS Handshake 100 ms Server Processing 98 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