Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!DOCTYPE html>
<html lang=en>
<head>
<link rel="icon" href="/assets/images/favicon.png" />
<!-- Basic Page Needs
================================================== -->
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<!-- Mobile Specific Metas
================================================== -->
<meta name="HandheldFriendly" content="True" />
<meta name="MobileOptimized" content="320" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<!-- Title and meta description
================================================== -->
<!-- Begin Jekyll SEO tag v2.8.0 -->
<title>The Americans with Disabilities Act | ADA.gov</title>
<meta name="generator" content="Jekyll v4.3.2" />
<meta property="og:title" content="The Americans with Disabilities Act" />
<meta property="og:locale" content="en_US" />
<meta name="description" content="Disability rights are civil rights. From voting to parking, the ADA is a law that protects people with disabilities in many areas of public life." />
<meta property="og:description" content="Disability rights are civil rights. From voting to parking, the ADA is a law that protects people with disabilities in many areas of public life." />
<link rel="canonical" href="https://www.ada.gov/" />
<meta property="og:url" content="https://www.ada.gov/" />
<meta property="og:site_name" content="ADA.gov" />
<meta property="og:image" content="https://www.ada.gov/assets/images/default-card.png" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary_large_image" />
<meta property="twitter:image" content="https://www.ada.gov/assets/images/default-card.png" />
<meta property="twitter:title" content="The Americans with Disabilities Act" />
<meta name="google-site-verification" content="34Ks265Uibpdda984RS0SxVABVZCdlVrdSp61pIdZQ8" />
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"WebSite","description":"Disability rights are civil rights. From voting to parking, the ADA is a law that protects people with disabilities in many areas of public life.","headline":"The Americans with Disabilities Act","image":{"asset":"default-card.png","url":"https://www.ada.gov/assets/images/default-card.png","@type":"imageObject"},"name":"ADA.gov","url":"https://www.ada.gov/"}</script>
<!-- End Jekyll SEO tag -->
<meta http-equiv="Content-Language" content="en" />
<meta name="searchgov_custom1" content="Disability rights are civil rights. From voting to parking, the ADA is a law that protects people with disabilities in many areas of public life." />
<meta name="dcterms.audience" content="" />
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations70 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN & DeliveryCloudflareREVIEW
A+DNS Records4 A records, 63 ms lookupPASS
| A | 172.65.90.26, 172.65.90.27, 172.65.90.25, 172.65.90.24 |
| AAAA | 2606:4700:78::90:0:182, 2606:4700:78::90:0:183, 2606:4700:78::90:0:181, 2606:4700:78::90:0:180 |
| CNAME | — |
| NS | novalee.ns.cloudflare.com, jonah.ns.cloudflare.com |
| MX | — |
| TXT | SPF v=spf1 -all _3whs352oaqjnh27ndonv3f1xugo7g4a |
| CAA | Lookup not available with standard resolver |
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.
ARedirect Chain1 redirect(s), 919 ms totalPASS
https://ada.gov
393 ms · HTTP/1.1
https://www.ada.gov/
527 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ada.gov | 301 | 393 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.ada.gov/ | 200 | 527 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+Domain Intelligenceada.gov — via get.gov, 24 years, 6 months oldPASS
13 days
July 25, 2026
70 days
Issued by CLOUDFLARE, INC.
24 years, 6 months
Registered February 25, 2002
Enabled
Protects against DNS spoofing
Unknown
2606:4700:78::90:0:183
get.gov
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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