Skip to content
https://science.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
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 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.

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
158 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 112 ms lookup
PASS
2 A records, 112 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 54.151.119.244, 52.8.62.150
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns01.aaas.org, ns03.aaas.org, ns02.aaas.org
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 112 ms
Got: 112 ms
A54.151.119.244, 52.8.62.150
AAAA
CNAME
NSns01.aaas.org, ns03.aaas.org, ns02.aaas.org
MX
TXT
google-site-verification=SkWtBkjBFidrXhb-kRNFCaurkZmZND_LpwYWIHSiY1k
google-site-verification=kOrRR8Wac1GleusKP0_rQEHEjg-3aSNn9Dm_KCJGblg
google-site-verification=LYYOBfzhTx6yq_g3EmkQvEkAFMpXJGfXzjCM7GW-uMo
CAALookup not available with standard resolver
Resolved in 112 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 851 ms total
PASS
1 redirect(s), 851 ms total
Info::
Single redirect
Got: https://science.org → https://www.science.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 851 ms total
Got: 851 ms

https://science.org

665 ms · HTTP/1.1

301

https://www.science.org/

186 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://science.org301665 msHTTP/1.1Apache/2.4.66 () PHP/7.4.33
2https://www.science.org/403186 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 930 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 930 B Sitemaps referenced 2 User-agents Twitterbot, GPTBot, ChatGPT-User, CCBot, Applebot-Extended, *, Google-Extended, anthropic-ai Blocking No — crawling allowed
Sitemap: https://www.science.org/sitemap_index.xml
Sitemap: https://www.science.org/sitemap-index-1.txt
User-agent: *
Disallow: /action
Disallow: /help
Disallow: /search
Disallow: /feedback
Disallow: /page/account-confirmation-thanks
Disallow: /media
Disallow: /medical-research
Disallow: /servlet/linkout
Disallow: /na101/
Disallow: /na101v1/
Disallow: /na102/
Disallow: /doi/mlt/
Disallow: /pb/widgets
Disallow: /author
Allow: /action/showFeed
Allow: /action/showJournal
Allow: /action/showPublications
Allow: /action/showXml
Allow: /action/showTopic
Allow: /action/showBook
Allow: /action/showCoverImage
Allow: /action/downloadSupplement

User-agent: Google-Extended
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Twitterbot
Allow: /

User-agent: GPTBot
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.science.org/
200https://science.org/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
science.org — via Network Solutions, LLC, 31 years, 7 months old, hosted on AWS
PASS
science.org — via Network Solutions, LLC, 31 years, 7 months old, hosted on AWS
Info::
Domain registered until Feb 24, 2029 (2 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: AWS
Got: AS16509
Domain expiry

955 days

February 24, 2029

SSL certificate

158 days

Issued by Amazon

Domain age

31 years, 7 months

Registered February 23, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.8.62.150

Registrar

Network Solutions, LLC

Unlocked 3 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 23, 1995 (31 years, 7 months ago)
Expires February 24, 2029 (2 years, 10 months)
Last Updated December 13, 2023
Name Servers ns01.aaas.org, ns02.aaas.org, ns03.aaas.org
DNSSEC Not enabled
Hosting
IP Address 52.8.62.150
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
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 748 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
113 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
158 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
317 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
748 ms
Total Time Total request time from DNS lookup through full response.
748 ms

Connection waterfall

DNS Lookup 113 ms TCP Connect 158 ms TLS Handshake 317 ms Server Processing 159 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