myheritage.com
As of Nov 6, 2026, myheritage.com's robots.txt blocks Bytespider and its DMARC policy is reject.
Checked daily since Oct 31, 2026. JSON. Link to this check. Run this site? Remove or correct this report.
Checked Nov 6, 2026, 23:14 UTC
| File | Status | What the robot saw | Same since |
|---|---|---|---|
| ads.txt | NOT_FOUND | Not found. The site answered 404. | 2026-10-31, first check |
| app-ads.txt | NOT_FOUND | Not found. The site answered 404. | 2026-11-03, first check |
| sellers.json | NOT_FOUND | Not found. The site answered 404. | 2026-11-05, first check |
| robots.txt | SUCCESS | 79 rules for 12 AI crawlers. Blocks Bytespider. | 2026-11-06, first check |
| llms.txt | NOT_FOUND | Not found. The site answered 404. | 2026-11-06, first check |
| DMARC | SUCCESS | p=reject, pct=100. Reports on. | 2026-11-06, first check |
| MTA-STS | NOT_FOUND | Not found. The site answered 404. | 2026-11-06, first check |
| BIMI | SUCCESS | Logo record published. | 2026-11-06, first check |
| security.txt | RESTRICTED | The site turned the robot away. No good check yet. |
These are the site's own public files, as fetched, with the date. The robot reports what is published. It does not judge compliance, approval, or intent. A failed fetch is a failed fetch, never a missing file.
Not checked: anything behind a login, account settings, or private feeds. Whether crawlers obey robots.txt. Business deals: a file line is not a contract.