main.jp
As of Nov 6, 2026, the robot has read 3 of main.jp's nine public files and shows the state of each.
Checked daily since Nov 6, 2026. JSON. Link to this check. Run this site? Remove or correct this report.
Checked Nov 6, 2026, 23:13 UTC
| File | Status | What the robot saw | Same since |
|---|---|---|---|
| ads.txt | UNAVAILABLE | Secure connection failed. No good check yet. UNAVAILABLE, NOT AN ABSENCE | |
| app-ads.txt | UNAVAILABLE | Secure connection failed. No good check yet. UNAVAILABLE, NOT AN ABSENCE | |
| sellers.json | UNAVAILABLE | Secure connection failed. No good check yet. UNAVAILABLE, NOT AN ABSENCE | |
| robots.txt | UNAVAILABLE | Secure connection failed. No good check yet. UNAVAILABLE, NOT AN ABSENCE | |
| llms.txt | UNAVAILABLE | Secure connection failed. No good check yet. UNAVAILABLE, NOT AN ABSENCE | |
| DMARC | SUCCESS | p=. Reports off. | 2026-11-06, first check |
| MTA-STS | NOT_FOUND | No MTA-STS record. | 2026-11-06, first check |
| BIMI | NOT_FOUND | No BIMI record. | 2026-11-06, first check |
| security.txt | UNAVAILABLE | Secure connection failed. No good check yet. UNAVAILABLE, NOT AN ABSENCE |
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.