findagrave.com
Domduck has read findagrave.com on 6 days across 5 sources, since 2 August 2026. The domain was registered in 1997. Its robots.txt blocks none of the 8 AI crawlers Domduck tracks.
Last checked .
Charts appear once there are seven days of readings.
blocked
What changed
6 days of readings- 29 September 2026 (2026-09-29)
- Applebot-Extended was unblocked between 15 September 2026 and 29 September 2026.
- Bytespider was unblocked between 15 September 2026 and 29 September 2026.
- CCBot was unblocked between 15 September 2026 and 29 September 2026.
- ClaudeBot was unblocked between 15 September 2026 and 29 September 2026.
- Google-Extended was unblocked between 15 September 2026 and 29 September 2026.
- GPTBot was unblocked between 15 September 2026 and 29 September 2026.
- robots.txt started redirecting to www.findagrave.com between 15 September 2026 and 29 September 2026.
- 31 August 2026 (2026-08-31)
- The certificate was renewed between 17 August 2026 and 31 August 2026 and is valid to 19 November 2026.
Popularity rank
73 days, lower is betterPosition in the Tranco list, a research ranking of the million most popular domains averaged over thirty days so a single day’s traffic spike cannot move it.
AI crawler policy
Redirects to www.findagrave.com · No llms.txtNo ChatGPT browsing or training
No ChatGPT search surface
No Claude retrieval
No Perplexity citation
Out of Gemini and AI Overviews grounding, Search ranking unaffected
Out of Apple Intelligence training
Out of most open training corpora
Out of TikTok and Doubao
Read from findagrave.com/robots.txt. “Not named” means the file says nothing about that agent, which is not the same as allowing it: a catch-all rule added later blocks it without anyone deciding to.
What the domain itself says
read directly, not from a vendor- Issuer
- Google Trust Services
- Valid
- Yes
- Expires
- 2026-11-19
- Protocol
- TLSv1.3
- Names covered
- 2
- A records
- 2
- AAAA records
- 2
- Mail exchangers
- 3
- Nameservers
- rick.ns.cloudflare.com, uma.ns.cloudflare.com
- DMARC policy
- reject
- Registered
- 1997-06-21
- Registrar
- MarkMonitor Inc.
- Registry status
- client delete prohibited, client transfer prohibited, client update prohibited
How findagrave.com compares to other .com domains
Questions
- Does findagrave.com block GPTBot?
- No. findagrave.com's robots.txt does not disallow GPTBot, though it does not name the agent either.
- Does findagrave.com publish an llms.txt file?
- No. Domduck found no llms.txt at findagrave.com.
- When was findagrave.com registered?
- 21 June 1997, through MarkMonitor Inc..
- Who issues findagrave.com's certificate?
- Google Trust Services.
How this page is made
Every number on this page is a measurement Domduck took itself or read from a public source, on a stated date. Nothing here is written by a language model. Where a value has not changed, no sentence is generated about it.
First reading . 5 sources, 6 days with at least one reading. The popularity rank comes from the Tranco list; the registration record from RDAP, which ICANN requires registries to publish. The certificate, the DNS records and the crawler policy are read by Domduck directly from findagrave.com.