Skip to content
https://ingentaconnect.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
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, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1214 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 1214 B Sitemaps referenced 0 User-agents GoogleBot, * Blocking No — crawling allowed
# 
# Agent-specific settings for indexing the site.
#
User-agent: GoogleBot
# Google ignores Crawl-delay
# Crawl-delay: 5
# URL prefixes
Disallow: /admin/
Disallow: /cart/
# Prevent scraping of a particular PDF
# /content/routledg/gwst/2003/00000032/00000004/art00003
# (disallow needs to be at directory level, ie issue level)
Disallow: /content/routledg/gwst/2003/00000032/00000004/
Disallow: /marked-list/
Disallow: /profile/
Disallow: /register/
Disallow: /search/
Disallow: /search;
Disallow: /search?
Disallow: /searching/Mark
Disallow: /searching/UnMark
Disallow: /session/
Disallow: /content/docdel/
Disallow: /validate/

# 
# Generic settings for indexing the site.
#
User-agent: *
Crawl-delay: 5
# URL prefixes
Disallow: /admin/
Disallow: /cart/
# Prevent scraping of a particular PDF
# /content/routledg/gwst/2003/00000032/00000004/art00003
# (disallow needs to be at directory level, ie issue level)
Disallow: /content/routledg/gwst/2003/00000032/00000004/
Disallow: /marked-list/
Disallow: /profile/
Disallow: /register/
Disallow: /search/
Disallow: /search;
Disallow: /search?
Disallow: /searching/Mark
Disallow: /searching/UnMark
Disallow: /session/
Disallow: /content/docdel/
Disallow: /validate/


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.ingentaconnect.com/
200https://ingentaconnect.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ingentaconnect.com/ https://ingentaconnect.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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
2 A records, 45 ms lookup
PASS
2 A records, 45 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.16.143, 104.18.17.143
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: lee.ns.cloudflare.com, elma.ns.cloudflare.com
Info::
3 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: 45 ms
Got: 45 ms
A104.18.16.143, 104.18.17.143
AAAA
CNAME
NSlee.ns.cloudflare.com, elma.ns.cloudflare.com
MX
10 mailhost1.ingenta.com
10 mailhost3.ingenta.com
10 mailhost2.ingenta.com
TXT
SPF v=spf1 include:ingenta.net ~all
google-site-verification=aGHuhpJGr_o3yhCk78d5HqlymemHuVTLUJk2AOb1N4E
CAALookup not available with standard resolver
Resolved in 45 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), 449 ms total
PASS
1 redirect(s), 449 ms total
Info::
Single redirect
Got: https://ingentaconnect.com → https://www.ingentaconnect.com/ (301)
Info::
WWW normalization redirect

https://ingentaconnect.com

202 ms · HTTP/1.1

301

https://www.ingentaconnect.com/

247 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ingentaconnect.com301202 msHTTP/1.1cloudflare
2https://www.ingentaconnect.com/200247 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
ingentaconnect.com — via GoDaddy.com, LLC, 22 years, 9 months old, hosted on Cloudflare
PASS
ingentaconnect.com — via GoDaddy.com, LLC, 22 years, 9 months old, hosted on Cloudflare
Info::
Domain registered until Nov 3, 2026 (6 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: GoDaddy.com, 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: Cloudflare
Got: AS13335
Domain expiry

140 days

November 3, 2026

SSL certificate

33 days

Issued by Google Trust Services

Domain age

22 years, 9 months

Registered November 3, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.17.143

Registrar

GoDaddy.com, LLC

Unlocked 2 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 GoDaddy.com, LLC
Created November 3, 2003 (22 years, 9 months ago)
Expires November 3, 2026 (6 months)
Last Updated October 21, 2024
Name Servers elma.ns.cloudflare.com, lee.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.18.17.143
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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 275 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
276 ms
Total Time Total request time from DNS lookup through full response.
276 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 200 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9effd1423d112a0a-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9effd1423d112a0a-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback