Skip to content
https://figshare.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
202 HTTP 202
Checks
9
5 PASS 3 REVIEW 1 FIX
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.

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

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::
HTTP version does not redirect to HTTPS
Got: HTTP 202 Expected: 301 redirect to HTTPS

www / non-www

202https://www.figshare.com/
200https://figshare.com/

HTTP → HTTPS

202http://figshare.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

247
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
3 A records, 265 ms lookup
PASS
3 A records, 265 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 54.154.21.168, 54.246.151.77, 63.35.39.28
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2a05:d018:1f4:d003:ac0a:4671:c64b:9dd2, 2a05:d018:1f4:d000:edb4:a90:6da6:f69f, 2a05:d018:1f4:d005:b6a4:2988:981c:5115
Info::
4 nameserver(s) configured
Got: ns-1455.awsdns-53.org, ns-1552.awsdns-02.co.uk, ns-194.awsdns-24.com, ns-884.awsdns-46.net
Info::
5 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
Warning::
DNS resolution is slow (265 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 265 ms
A54.154.21.168, 54.246.151.77, 63.35.39.28
AAAA2a05:d018:1f4:d003:ac0a:4671:c64b:9dd2, 2a05:d018:1f4:d000:edb4:a90:6da6:f69f, 2a05:d018:1f4:d005:b6a4:2988:981c:5115
CNAME
NSns-1455.awsdns-53.org, ns-1552.awsdns-02.co.uk, ns-194.awsdns-24.com, ns-884.awsdns-46.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
MS=ms64885905
UK-federation-domain-verification=66af4f4bc47c07a6eade6803a6e9a5f8
access-domain-verification=a19bcdad7b8fe5d58adc680619d6ae0ed8cea58c20382b253bebb...
anthropic-domain-verification-sz90ng=R0RzGEcTa3cMbvMPgH1NyneOC
atlassian-domain-verification=vujOqKgTa3qfzkMqa3sYB93w6sf0XaNYcystg60SWUA7CmiVHw...
coda-verification=265d50f8-9277-416c-9114-4663471f079a
google-site-verification=BUPZldDzynyEwL25Pigd-3KvX9NEBIVs_xmzCvjvUSI
google-site-verification=IKi55yRibJTwIhL1ERLqHACdJLpa54lLVVqJYq7UYbM
google-site-verification=OB2zQtcbcNxWFMq0oYptXmYNlBjdIfhd4oM4qKtMasA
google-site-verification=dn9vDb-I1ZzOWXtlXJjg48d6zAtC85AQs5t5XWNpws4
knowbe4-site-verification=c20565b6b79a0be4a2685d8bfd5f23f0
pardot533712=943ba2710db4a61be2e7b1420c8cd64a58c1e6b525c2768850ae97c7b282aeab
status-page-domain-verification=s6xx5jfv7g6b
SPF v=spf1 include:amazonses.com include:_spf.google.com include:servers.mcsv.net in...
CAALookup not available with standard resolver
Resolved in 265 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://figshare.com

https://figshare.com

648 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://figshare.com202648 msHTTP/1.1awselb/2.0
A+
IPv6 Readiness
IPv6 reachable (245 ms)
PASS
IPv6 reachable (245 ms)
Info::
IPv6 is configured and reachable at 2a05:d018:1f4:d003:ac0a:4671:c64b:9dd2, 2a05:d018:1f4:d000:edb4:a90:6da6:f69f, 2a05:d018:1f4:d005:b6a4:2988:981c:5115
Got: 245 ms connect
IPv6 Ready
AAAA Records 2a05:d018:1f4:d003:ac0a:4671:c64b:9dd2, 2a05:d018:1f4:d000:edb4:a90:6da6:f69f, 2a05:d018:1f4:d005:b6a4:2988:981c:5115 Connection Reachable (245 ms)
A+
Domain Intelligence
figshare.com — via Amazon Registrar, Inc., 15 years, 7 months old
PASS
figshare.com — via Amazon Registrar, Inc., 15 years, 7 months old
Info::
Domain registered until Dec 7, 2026 (7 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: Amazon Registrar, 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

175 days

December 7, 2026

SSL certificate

247 days

Issued by Amazon

Domain age

15 years, 7 months

Registered December 7, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a05:d018:1f4:d000:edb4:a90:6da6:f69f

Registrar

Amazon Registrar, 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 Amazon Registrar, Inc.
Created December 7, 2010 (15 years, 7 months ago)
Expires December 7, 2026 (7 months)
Last Updated November 20, 2025
Name Servers ns-1455.awsdns-53.org, ns-1552.awsdns-02.co.uk, ns-194.awsdns-24.com, ns-884.awsdns-46.net
DNSSEC Not enabled
Hosting
IP Address 2a05:d018:1f4:d000:edb4:a90:6da6:f69f
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 51 ms TCP Connect 196 ms TLS Handshake 198 ms Server Processing 198 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