humans.txt file
A file at /humans.txt naming the people who built the site. Purely a courtesy.
humans.txt is an informal initiative from 2011: a plain-text file in the site root that credits the people behind the site — designers, developers, writers — and sometimes lists the tools and standards used to build it. It is the human counterpart of robots.txt, written for curious visitors rather than for crawlers.
It has no effect on search ranking, security or performance, and nothing reads it automatically. The report lists it only as a courtesy: published or not published, never a warning.
How SiteScan checks
The scan requests /humans.txt without following redirects and counts it as published when the answer is a 200 with a non-empty body that is not an HTML page. A site that answers every unknown address with its homepage is therefore not mistaken for having one.
How to add one
There is no strict format. A common layout uses short sections:
/* TEAM */with names, roles and where to find each person/* THANKS */for contributors/* SITE */with the last update date, languages and the main technologies
Serve it as text/plain and, if you like, reference it from the page head with a rel="author" link. If you want a file that is actually useful to someone in need, add security.txt first.
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