Skip to content
https://nature.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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
Redirect Chain
2 redirect(s), 768 ms total
REVIEW
2 redirect(s), 768 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Redirect overhead: 768 ms total
Got: 768 ms

https://nature.org

532 ms · HTTP/1.1

301

https://www.nature.org/

206 ms · HTTP/1.1

301

https://www.nature.org/en-us/

30 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nature.org301532 msHTTP/1.1Apache/2.4.66 (Ubuntu)
2https://www.nature.org/301206 msHTTP/1.1Apache
3https://www.nature.org/en-us/20030 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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
TLS Certificate Expiry & Recommendations
60 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

60
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
2 A records, 33 ms lookup
PASS
2 A records, 33 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 44.252.241.121, 44.253.236.176
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1343.awsdns-39.org, ns-306.awsdns-38.com, ns-2021.awsdns-60.co.uk, ns-925.awsdns-51.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: 33 ms
Got: 33 ms
A44.252.241.121, 44.253.236.176
AAAA
CNAME
NSns-1343.awsdns-39.org, ns-306.awsdns-38.com, ns-2021.awsdns-60.co.uk, ns-925.awsdns-51.net
MX
10 us-smtp-inbound-1.mimecast.com
10 us-smtp-inbound-2.mimecast.com
TXT
SPF v=spf1 mx:tnc.org include:outboundmail.blackbaud.net include:servers.mcsv.net in...
6t83gssmxkpd2dn5pm3fn0lccj2hbwff
google-site-verification=6ipPuwGoKra6s49JT7KY-OJCHOG0-G4HBheO0o7GHxA
facebook-domain-verification=9xkg4y9f2h9bgxx49rk37kfc4ztu5h
MS=ms23779551
CAALookup not available with standard resolver
Resolved in 33 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+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 211 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 references sitemap
robots.txt 200 OK
Size 211 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# https://www.nature.org/

User-agent: *
Disallow: /config/
Disallow: /interstitialredirectmodalurl/
Disallow: /interstitialRedirectModalURL/
Disallow: /search/

Sitemap: https://www.nature.org/sitemap-index.xml
sitemap.xml 200 OK
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.nature.org/
200https://nature.org/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
nature.org — via Amazon Registrar, Inc., 30 years, 4 months old, hosted on AWS
PASS
nature.org — via Amazon Registrar, Inc., 30 years, 4 months old, hosted on AWS
Info::
Domain registered until May 16, 2030 (4 years, 1 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

1432 days

May 16, 2030

SSL certificate

60 days

Issued by Let's Encrypt

Domain age

30 years, 4 months

Registered May 15, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

44.253.236.176

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 May 15, 1996 (30 years, 4 months ago)
Expires May 16, 2030 (4 years, 1 months)
Last Updated March 24, 2025
Name Servers ns-1343.awsdns-39.org, ns-2021.awsdns-60.co.uk, ns-306.awsdns-38.com, ns-925.awsdns-51.net
DNSSEC Not enabled
Hosting
IP Address 44.253.236.176
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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

Connection waterfall

DNS Lookup 34 ms TCP Connect 172 ms TLS Handshake 178 ms Server Processing 172 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