Skip to content
https://clever.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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.clever.com/
200https://clever.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://clever.com/ https://clever.com/

Consistent

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

Certificate validity

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

Recommended actions

  • 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
4 A records, 34 ms lookup
PASS
4 A records, 34 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.249.228.72, 13.249.228.64, 13.249.228.79, 13.249.228.17
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-432.awsdns-54.com, ns-887.awsdns-46.net, ns-1197.awsdns-21.org, ns-1579.awsdns-05.co.uk
Info::
5 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: 34 ms
Got: 34 ms
A13.249.228.72, 13.249.228.64, 13.249.228.79, 13.249.228.17
AAAA
CNAME
NSns-432.awsdns-54.com, ns-887.awsdns-46.net, ns-1197.awsdns-21.org, ns-1579.awsdns-05.co.uk
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
anthropic-domain-verification-mr5c9k=i19u8DRx8hvIIhhtwaRUVURcR
zapier-domain-verification-challenge=a2eb9754-54f9-410f-a033-7a9297d8f5e7
status-page-domain-verification=w22p8xtvd84s
wpe-verification=clever1
apple-domain-verification=JfLmlB47OGvuAY3B
mongodb-site-verification=Ldk5KiDHKpBj6S31LEkN0dOHUo00NnR2
docusign=71bebef5-d6bd-4be4-bb1a-371b4fb5354a
linear-domain-verification=kdmrgvk26qsu
SPF v=spf1 include:spf.mandrillapp.com include:_spf.google.com include:amazonses.com...
google-site-verification=b95M_eJWY9Clc_mpT4fi2vHX0uHheHfx53wlHKNv--M
CAALookup not available with standard resolver
Resolved in 34 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
1 redirect(s), 757 ms total
PASS
1 redirect(s), 757 ms total
Info::
Single redirect
Got: https://clever.com → https://www.clever.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 757 ms total
Got: 757 ms

https://clever.com

233 ms · HTTP/1.1

301

https://www.clever.com/

524 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://clever.com301233 msHTTP/1.1AmazonS3
2https://www.clever.com/200524 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 149 URLs
PASS
robots.txt present, sitemap with 149 URLs
Info::
robots.txt is present
Got: 164 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 149 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 164 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /craft/
Disallow: /vendor/
Disallow: /schools/signup
Disallow: /signup
Disallow: /appstore/orders/

Sitemap: https://clever.com/sitemap.xml

A+
Domain Intelligence
clever.com — via Name.com, Inc., 31 years, 6 months old, hosted on AWS
PASS
clever.com — via Name.com, Inc., 31 years, 6 months old, hosted on AWS
Info::
Domain registered until Mar 10, 2027 (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: Name.com, Inc.
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

241 days

March 10, 2027

SSL certificate

191 days

Issued by Amazon

Domain age

31 years, 6 months

Registered March 9, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.249.228.17

Registrar

Name.com, Inc.

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 Name.com, Inc.
Created March 9, 1995 (31 years, 6 months ago)
Expires March 10, 2027 (10 months)
Last Updated February 12, 2018
Name Servers ns-1197.awsdns-21.org, ns-1579.awsdns-05.co.uk, ns-432.awsdns-54.com, ns-887.awsdns-46.net
DNSSEC Not enabled
Hosting
IP Address 13.249.228.17
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 269 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.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
269 ms
Total Time Total request time from DNS lookup through full response.
270 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 200 ms Content Transfer 0 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG50-P6)
Got: x-amz-cf-id: 3PNHS18_mJqOJCbkeLtMc9lddLzxX195_AmcGClYEt8rnhS0nBw_EA==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: 3PNHS18_mJqOJCbkeLtMc9lddLzxX195_AmcGClYEt8rnhS0nBw_EA==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback