Skip to content
https://lever.co

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
3
PASS
4
INFO
1
Probed from Santa Clara, United States
302 Found
Checks
9
4 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.lever.co/
200https://lever.co/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://lever.co/ → https://lever.co/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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, 66 ms lookup
PASS
2 A records, 66 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.248.159.192, 76.223.22.197
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1281.awsdns-32.org, ns-1577.awsdns-05.co.uk, ns-509.awsdns-63.com, ns-756.awsdns-30.net
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: 66 ms
Got: 66 ms
A13.248.159.192, 76.223.22.197
AAAA—
CNAME—
NSns-1281.awsdns-32.org, ns-1577.awsdns-05.co.uk, ns-509.awsdns-63.com, ns-756.awsdns-30.net
MX
10 lever-co.mail.protection.outlook.com
TXT
MS=F873D01E04F3407EE0E0AF01EB2B0DA8D3996875
MS=ms26677540
MS=ms85638047
adobe-idp-site-verification=0675f766d1eda8744069719efc5515de9d6dbf425b9e5df61c82...
apple-domain-verification=3ZeO25jjBZA1XmJm
atlassian-domain-verification=eTczF+OLBKaqLwtqi61vktk+mk6a/JwaAVr+twREDAR7kjMseQ...
docusign=3071fed0-be36-4975-a19b-c4b7c65613c2
docusign=744fdb1d-f953-452b-ad11-31805f10963e
docusign=d867ceae-31f9-74e9-a657-eb9813f207d9
google-site-verification=-wFNfJ8wZleHaCWZ0_XCyg82uRBKUmYWpaLaLXbLsv0
google-site-verification=0yTePG03Savt-_ym44SN60tjFLj1HV_qV7yu40x57Ss
google-site-verification=AZo2HrAVKwR1jGTxyyQnn6C2ZUZwCY9OctHimZPyjxw
google-site-verification=bQG1NsuKzTbDHQMgqAt5iHFy7ITQ6kQQFWo0wvzp_N8
google-site-verification=lYemFJ-sdQxKubsLcY17-O6YiUw2OrvAAWWh5L_vtpE
google-site-verification=mWNNv3lTCr2plLgxpo8OPaGUXVWVN4DlHFAA81QxCsY
google-site-verification=mei0Wse_0N5ddMDqv5KIh__J1qHXv_FhfyUKVcAXDP4
google-site-verification=zpyhQtcB4JiZJRD5mboq6O6yh7Y4DJob1zHfLdcGzsM
parallels-domain-verification=613572854b5e4275981e96996b89cf2c587c3a3980cb4a83b7...
status-page-domain-verification=cml50gmcj5d6
SPF v=spf1 include:_spf.google.com include:mail.zendesk.com include:mktomail.com inc...
CAALookup not available with standard resolver
Resolved in 66 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), 204 ms total
PASS
1 redirect(s), 204 ms total
Info::
Single redirect
Got: https://lever.co → https://www.lever.co/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://lever.co

https://lever.co

102 ms · HTTP/1.1

302

https://www.lever.co/

102 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lever.co302102 msHTTP/1.1
2https://www.lever.co/200102 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 172 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
Sitemap index with 14 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 172 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /wp-admin/admin-ajax.php
Allow: /wp-admin/images/*
Disallow: /wp-admin/
Disallow: /readme.html
Disallow: /license.txt
Disallow: /?s=*
Disallow: /*.pdf$
sitemap.xml 200 OK
Type Sitemap Index URLs 14 entries Valid XML Yes
Child Sitemaps:
A+
HTTP Probe Timing
Total 118 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
22 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
69 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
118 ms
Total Time Total request time from DNS lookup through full response.
118 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 3 ms TLS Handshake 69 ms Server Processing 25 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback