Skip to content
https://ripe.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
4 PASS 4 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
1 redirect(s), 1707 ms total
REVIEW
1 redirect(s), 1707 ms total
Info::
Single redirect
Got: https://ripe.net → https://www.ripe.net/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1707 ms total
Got: 1707 ms

https://ripe.net

897 ms · HTTP/1.1

301

https://www.ripe.net/

811 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ripe.net301897 msHTTP/1.1nginx
2https://www.ripe.net/200811 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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.ripe.net/
200https://ripe.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ripe.net/ https://www.ripe.net/

Consistent

B
HTTP Probe Timing
Total 884 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
299 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
194 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
197 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
884 ms
Total Time Total request time from DNS lookup through full response.
884 ms

Connection waterfall

DNS Lookup 299 ms TCP Connect 194 ms TLS Handshake 197 ms Server Processing 194 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
87 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 297 ms lookup
PASS
1 A records, 297 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.0.11.51
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2001:67c:2e8:25::c100:b33
Info::
5 nameserver(s) configured
Got: ns3.lacnic.net, ns3.afrinic.net, ns4.apnic.net, manus.authdns.ripe.net, rirns.arin.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
Warning::
DNS resolution is slow (297 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 297 ms
A193.0.11.51
AAAA2001:67c:2e8:25::c100:b33
CNAME
NSns3.lacnic.net, ns3.afrinic.net, ns4.apnic.net, manus.authdns.ripe.net, rirns.arin.net
MX
10 mail-mx-1.ripe.net
10 mail-mx-2.ripe.net
TXT
MS=ms67751268
_3wvnerwv6j7cjao9jlahbjz2rawnoyo
c36nlg98h32mxgwrbtz64y39018my6nd
ZOOM_verify_dPvgSmAFSuKoW25ykWqtfw
sendinblue-site-verification=2659830
apple-domain-verification=hv6DqD0eixJVkv6U
status-page-domain-verification=qchkrfl7cvf2
jamf-site-verification=uCzTUcUzhZPNK3iyW7XJTQ
canva-site-verification=OXBJeXuzzmyUDU6WSHl0Ng
Sendinblue-code:d850df5c8b2bd24ad6e9574a894923c8
1password-site-verification=A5TCA342Y5EKBHWQ4TIY6JGY6U
onetrust-domain-verification=5b56bd2f7a8e49c08ac2ada053e80797
slack-domain-verification=QptqrRufWKeDJ1y3mG0kPOaXJj9ApWlaLvPtTcaV
google-site-verification=8brVsJvMeSvFzAIgUz-1bsBnkYURhzGe5DypAEmTPcI
google-site-verification=9zU35i5d8RKlwcp3slIZY5tvyyaId9Pjfo-4HOUIJtg
google-site-verification=Jl1ZA-AqhDLpL0vMBeFun9-qY3T58aHRe6sqCdj4iAk
google-site-verification=Mjh2VRqOuHsP4hbQDoA_flEskh-6S-YlFNrqGWayXAg
adobe-idp-site-verification=9dc07873a943b8b6ea812fb3747cb4e8332ef61d8450a61cef6b...
atlassian-domain-verification=gald0QJawuRiDwOWptmExBQ/fIHLfDUHAKzhiRiJXTDHEGHWb0...
SPF v=spf1 ip4:193.0.19.0/24 ip6:2001:67c:2e8:11::/64 include:mail.zendesk.com inclu...
CAALookup not available with standard resolver
Resolved in 297 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.

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+
IPv6 Readiness
IPv6 reachable (192 ms)
PASS
IPv6 reachable (192 ms)
Info::
IPv6 is configured and reachable at 2001:67c:2e8:25::c100:b33
Got: 192 ms connect
IPv6 Ready
AAAA Records 2001:67c:2e8:25::c100:b33 Connection Reachable (192 ms)
A+
Crawlability
robots.txt present, sitemap with 9429 URLs
PASS
robots.txt present, sitemap with 9429 URLs
Info::
robots.txt is present
Got: 234 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9429 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 234 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /ripe/mail/archives/agm-nominations/
Disallow: /ripe/mail/archives/members-discuss-unmoderated/
Disallow: /ripe/mail/archives/ripe-list-unmoderated/
Disallow: /search/
Sitemap: https://www.ripe.net/sitemap.xml

A+
Domain Intelligence
ripe.net — via Gandi SAS, 34 years, 7 months old
PASS
ripe.net — via Gandi SAS, 34 years, 7 months old
Info::
Domain registered until Feb 26, 2027 (10 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Gandi SAS
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

255 days

February 26, 2027

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

34 years, 7 months

Registered February 25, 1992

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2001:67c:2e8:25::c100:b33

Registrar

Gandi SAS

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gandi SAS
Created February 25, 1992 (34 years, 7 months ago)
Expires February 26, 2027 (10 months)
Last Updated March 17, 2026
Name Servers manus.authdns.ripe.net, ns3.afrinic.net, ns3.lacnic.net, ns4.apnic.net, rirns.arin.net
DNSSEC Enabled
Hosting
IP Address 2001:67c:2e8:25::c100:b33
Data source: rdap (0.4s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback