Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1707 ms totalREVIEW
https://ripe.net
897 ms · HTTP/1.1
https://www.ripe.net/
811 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ripe.net | 301 | 897 ms | HTTP/1.1 | nginx |
| 2 | https://www.ripe.net/ | 200 | 811 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BHTTP Probe TimingTotal 884 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations87 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
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
ADNS Records1 A records, 297 ms lookupPASS
| A | 193.0.11.51 |
| AAAA | 2001:67c:2e8:25::c100:b33 |
| CNAME | — |
| NS | ns3.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... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
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.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+IPv6 ReadinessIPv6 reachable (192 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 9429 URLsPASS
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 Intelligenceripe.net — via Gandi SAS, 34 years, 7 months oldPASS
255 days
February 26, 2027
87 days
Issued by Let's Encrypt
34 years, 7 months
Registered February 25, 1992
Enabled
Protects against DNS spoofing
Unknown
2001:67c:2e8:25::c100:b33
Gandi SAS
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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