Well-known change-password URL
A redirect at /.well-known/change-password pointing at the site's own change-password page, so a password manager can offer to rotate a saved password in one click. Only useful on a site with accounts, so the row only appears where the scan found a sign-in — a password field or a link to one.
/.well-known/change-password is a W3C convention that lets password managers send users straight to the page where they can change their password. When a manager finds a weak, reused or leaked password, it can offer a "Change password" button that opens exactly the right page instead of leaving the user to hunt through account settings. Safari, Chrome, 1Password and other managers support it.
The address is not a page itself — it is defined as a redirect to wherever your site actually handles password changes.
How SiteScan checks
This row appears only if the crawl found something to sign in to: a password field or a link to a login page. On sites without accounts the address is not requested at all. The scan asks for /.well-known/change-password without following redirects and counts it as published when the answer is a 3xx with a non-empty Location header. A 200 page, a 404 or a redirect-less answer reads as not published. It is optional, so absence is never shown as an error.
How to set it up
Add one redirect rule, for example in nginx location = /.well-known/change-password { return 302 /account/password; }, or Redirect 302 /.well-known/change-password /account/password in Apache. If changing the password requires being logged in, point it at the page anyway; the site's own login redirect will handle the rest. See also security.txt.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Well-known files”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data