Skip to content
https://sucuri.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 REVIEW
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.sucuri.net/
200https://sucuri.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://sucuri.net/ https://sucuri.net/

Consistent

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

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 113 ms lookup
PASS
2 A records, 113 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 192.124.249.16, 192.124.249.21
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:fe80:1010::16, 2a02:fe80:1010::21
Info::
6 nameserver(s) configured
Got: 11.sucuridns.com, 13.sucuridns.com, 10.sucuridns.com, 14.sucuridns.com, 12.sucuridns.com, 15.sucuridns.com
Info::
4 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: 113 ms
Got: 113 ms
A192.124.249.16, 192.124.249.21
AAAA2a02:fe80:1010::16, 2a02:fe80:1010::21
CNAME
NS11.sucuridns.com, 13.sucuridns.com, 10.sucuridns.com, 14.sucuridns.com, 12.sucuridns.com, 15.sucuridns.com
MX
1 ASPMX.L.GOOGLE.com
5 ALT1.ASPMX.L.GOOGLE.com
5 ALT2.ASPMX.L.GOOGLE.com
10 ASPMX2.GOOGLEMAIL.com
TXT
8tgqhgboklp7n9n4c01crh8deg
kqvf3m3asnpj1jkpdqa4qn1ajj
rpvalfm1t326kcum31mgg8hq2r
aae03ui7renstkv5flr4vst9da
87mffcr38g4o4l2i0fikfpifvl
nf3riq12a07afd22lcdnklo4fq
3637f31ukk4rmkop5eula407qb
SPF v=spf1 ip4:96.126.106.125 include:helpscoutemail.com include:_spf.google.com inc...
v6ho156qj5fu41af0o5dk02apt
CAALookup not available with standard resolver
Resolved in 113 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://sucuri.net

https://sucuri.net

92 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sucuri.net20092 msHTTP/1.1Sucuri/Cloudproxy
A+
IPv6 Readiness
IPv6 reachable (29 ms)
PASS
IPv6 reachable (29 ms)
Info::
IPv6 is configured and reachable at 2a02:fe80:1010::16, 2a02:fe80:1010::21
Got: 29 ms connect
IPv6 Ready
AAAA Records 2a02:fe80:1010::16, 2a02:fe80:1010::21 Connection Reachable (29 ms)
A+
Crawlability
robots.txt present, sitemap with 11 URLs
PASS
robots.txt present, sitemap with 11 URLs
Info::
robots.txt is present
Got: 24 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11 entries
Info::
Sitemap index with 11 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 24 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow:

A+
Domain Intelligence
sucuri.net — via GoDaddy.com, LLC, 17 years, 2 months old
PASS
sucuri.net — via GoDaddy.com, LLC, 17 years, 2 months old
Info::
Domain registered until Apr 24, 2029 (3 years 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: GoDaddy.com, 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.
Domain expiry

1044 days

April 24, 2029

SSL certificate

158 days

Issued by GoDaddy.com, Inc.

Domain age

17 years, 2 months

Registered April 24, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:fe80:1010::21

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created April 24, 2009 (17 years, 2 months ago)
Expires April 24, 2029 (3 years)
Last Updated April 21, 2023
Name Servers 10.sucuridns.com, 11.sucuridns.com, 12.sucuridns.com, 13.sucuridns.com
DNSSEC Not enabled
Hosting
IP Address 2a02:fe80:1010::21
Data source: rdap (0.1s)

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 166 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 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.
29 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
115 ms
Total Time Total request time from DNS lookup through full response.
167 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 26 ms TLS Handshake 29 ms Server Processing 29 ms Content Transfer 52 ms
A+
CDN & Delivery
Sucuri (HIT)
PASS
Sucuri (HIT)
Info::
Site is served via Sucuri CDN
Got: x-sucuri-id: 21017
Info::
CDN cache status: HIT
CDN Detected: Sucuri
Provider Sucuri Cache Status HIT Evidence x-sucuri-id: 21017
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback