Skip to content
https://royalsociety.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
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.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://royalsociety.org/ https://royalsociety.org/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
1 A records, 54 ms lookup
PASS
1 A records, 54 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 131.145.23.143
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1316.awsdns-36.org, ns-176.awsdns-22.com, ns-988.awsdns-59.net, ns-1630.awsdns-11.co.uk
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: 54 ms
Got: 54 ms
A131.145.23.143
AAAA
CNAME
NSns-1316.awsdns-36.org, ns-176.awsdns-22.com, ns-988.awsdns-59.net, ns-1630.awsdns-11.co.uk
MX
0 royalsociety-org.mail.protection.outlook.com
TXT
SPF v=spf1 ip4:194.81.217.225 ip4:103.254.236.195 include:customers.clickdimensions....
CAALookup not available with standard resolver
Resolved in 54 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://royalsociety.org

https://royalsociety.org

152 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://royalsociety.org200152 msHTTP/1.1Microsoft-IIS/10.0
A+
Crawlability
robots.txt present, sitemap with 5092 URLs
PASS
robots.txt present, sitemap with 5092 URLs
Info::
robots.txt is present
Got: 196 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5092 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 196 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

Disallow: /search#?query=

Disallow: /Blog/tagsearchresult/?

sitemap: https://royalsociety.org/sitemap.xml

sitemap: https://royalsociety.org/sitemaps/sitemap_content.xml
A
Domain Intelligence
royalsociety.org — via eNom, LLC, 26 years, 2 months old, hosted on Microsoft Azure
PASS
royalsociety.org — via eNom, LLC, 26 years, 2 months old, hosted on Microsoft Azure
Warning::
Domain expires in 61 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 23, 2026
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: eNom, 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: Microsoft Azure
Got: AS8075
Domain expiry

EXPIRED

June 23, 2026

SSL certificate

327 days

Issued by Sectigo Limited

Domain age

26 years, 2 months

Registered June 23, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

131.145.23.143

Registrar

eNom, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar eNom, LLC
Created June 23, 2000 (26 years, 2 months ago)
Expires June 23, 2026 (2 months)
Last Updated April 29, 2023
Name Servers ns-1316.awsdns-36.org, ns-1630.awsdns-11.co.uk, ns-176.awsdns-22.com, ns-988.awsdns-59.net
DNSSEC Not enabled
Hosting
IP Address 131.145.23.143
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.5s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 60 ms TCP Connect 26 ms TLS Handshake 27 ms Server Processing 107 ms Content Transfer 49 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback