Skip to content
https://jstor.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
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: 1605 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 1605 B Sitemaps referenced 1 User-agents Google-Extended, Googlebot, *, ClaudeBot, CCBot, GPTBot Blocking No — crawling allowed
Sitemap: https://www.jstor.org/sitemap.xml

User-agent: Googlebot
Disallow: /action
Disallow: /api
Disallow: /citation
Disallow: /clockss-manifest
Disallow: /doi/abs
Disallow: /feedback
Disallow: /purchase
Disallow: /register/
Disallow: /stable/full
Disallow: /stable/suppl
Disallow: /stable/view
Disallow: /start-session
Disallow: /stoken
Disallow: /tc/accept
Disallow: /token
Disallow: /topic
Disallow: /ui_log
Disallow: /userimages
Allow: /action/showLogin
Allow: /action/showJournal
Allow: /action/showPublication
Allow: /action/showSubscriptionJournalsAsXml
Allow: /action/showXml
Allow: /doi/xml

User-agent: *
Disallow: /action
Disallow: /api
Disallow: /citation
Disallow: /clockss-manifest
Disallow: /doi/abs
Disallow: /doi/xml
Disallow: /feedback
Disallow: /purchase
Disallow: /register/
Disallow: /stable/full
Disallow: /stable/suppl
Disallow: /stable/view
Disallow: /start-session
Disallow: /stoken
Disallow: /tc/accept
Disallow: /token
Disallow: /topic
Disallow: /ui_log
Disallow: /userimages
Allow: /action/showLogin
Allow: /action/showJournal
Allow: /action/showPublication
Allow: /action/showSubscriptionJournalsAsXml
Allow: /action/showXml

# Disallow crawling for the purposes of training models

# https://support.anthropic.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler
User-agent: ClaudeBot
# https://commoncrawl.org/faq
User-agent: CCBot
# https://platform.openai.com/docs/gptbot
User-agent: GPTBot
# https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers
User-agent: Google-Extended
Disallow: /

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.jstor.org/
200https://jstor.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://jstor.org/ https://www.jstor.org/

Consistent

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

Certificate validity

132
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
A+
DNS Records
4 A records, 105 ms lookup
PASS
4 A records, 105 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.0.152, 151.101.64.152, 151.101.192.152, 151.101.128.152
Info::
No IPv6 (AAAA) records
Info::
7 nameserver(s) configured
Got: usnjpr2ns02.ithaka.org, usmiaa1ns03.ithaka.org, usnjpr2ns04.ithaka.org, usnjpr2ns01.ithaka.org, usaeaz1ns03.ithaka.org, usaeaz1ns05.ithaka.org, usnyny1ns05.ithaka.org
Info::
1 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: 105 ms
Got: 105 ms
A151.101.0.152, 151.101.64.152, 151.101.192.152, 151.101.128.152
AAAA
CNAME
NSusnjpr2ns02.ithaka.org, usmiaa1ns03.ithaka.org, usnjpr2ns04.ithaka.org, usnjpr2ns01.ithaka.org, usaeaz1ns03.ithaka.org, usaeaz1ns05.ithaka.org, usnyny1ns05.ithaka.org
MX
10 IthakaHarbors-org.mail.protection.outlook.com
TXT
pardot1053043=4a6c81f133c99f6b859af420931577c383a1b1cd4e153d11ddb1b150a902b382
MS=ms59722565
facebook-domain-verification=t7mhq4udodhlfom0rn909rrhmrcq7f
google-site-verification=fUzFvqROnu3S1gFEmkwguY42PzRgOFzwg4qQMP24sU4
SPF v=spf1 mx include:spf.protection.outlook.com include:_spf.act-on.net include:u...
_globalsign-domain-verification=-lBuNJDFRxDkLkNbYOLBU03PlWjnPqAzBPAVUokhAw
k9s299b65mfuu3atd268noj595.
openai-domain-verification=dv-EAO0jUA8iKZCqlqYfddXpA3R
sending_domain1053043=a4a2b757167b9ba217895b3e2bb19f3873b9db5b7c0e9b4c6dd2c98c32...
CAALookup not available with standard resolver
Resolved in 105 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), 284 ms total
PASS
1 redirect(s), 284 ms total
Info::
Single redirect
Got: https://jstor.org → https://www.jstor.org/ (301)
Info::
WWW normalization redirect

https://jstor.org

4 ms · HTTP/1.1

301

https://www.jstor.org/

279 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://jstor.org3014 msHTTP/1.1Varnish
2https://www.jstor.org/200279 msHTTP/1.1envoy

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
jstor.org — via Network Solutions, LLC, 30 years, 7 months old, hosted on Fastly
PASS
jstor.org — via Network Solutions, LLC, 30 years, 7 months old, hosted on Fastly
Info::
Domain registered until Feb 17, 2031 (4 years, 10 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: Network Solutions, LLC
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: Fastly
Got: AS54113
Domain expiry

1679 days

February 17, 2031

SSL certificate

132 days

Issued by GlobalSign nv-sa

Domain age

30 years, 7 months

Registered February 16, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.192.152

Registrar

Network Solutions, LLC

Unlocked 7 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 Network Solutions, LLC
Created February 16, 1996 (30 years, 7 months ago)
Expires February 17, 2031 (4 years, 10 months)
Last Updated March 25, 2026
Name Servers usnjpr2ns02.ithaka.org, usmiaa1ns03.ithaka.org, usnjpr2ns04.ithaka.org, usnjpr2ns01.ithaka.org, usnyny1ns05.ithaka.org, usaeaz1ns03.ithaka.org, usaeaz1ns05.ithaka.org
DNSSEC Not enabled
Hosting
IP Address 151.101.192.152
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.7s)

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 252 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
247 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 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.
252 ms
Total Time Total request time from DNS lookup through full response.
252 ms

Connection waterfall

DNS Lookup 247 ms TCP Connect 0 ms TLS Handshake 4 ms Server Processing 1 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350049-TOJ
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-toj-leto2350049-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback