palisade.email
CrawlCheck last read palisade.email on 2026-11-16 and graded it C, 85 of 100, for how well AI agents and search crawlers can read it, with 8 findings.
llms.txtagents.mdMedia kitEntity graphAI access policyAgent-callable
Owner not verified. Is this your site? Prove it is yours — free, by DNS TXT or a meta tag.
Facts on record
| Fact | Value | How it is known |
|---|---|---|
| Owner | Not verified | nobody has proved they run this site |
| Grade | C, 85 of 100 | measured on the last read |
| Last read | 2026-11-16 | the date CrawlCheck fetched the site |
Get these 8 findings fixed
Every defect this row counts, corrected on the site itself and then re-measured from the outside — done is measured, not asserted. One-time, $100 for one small-business site, thirty days of monitoring included.
Get this fixed — $100Claiming is free and changes nothing but the owner mark. What a licence adds is the record behind this entry: re-measured twice a day, finding age on every defect, change receipts between any two dates. Keep it on the daily record.
What the fetch found
| Finding | Severity |
|---|---|
| robots.txt rules do not apply to named agents | 3 of 5 |
| Almost nothing a machine receives from this page is readable text | 3 of 5 |
| Links send crawlers to the same pages under many different addresses | 2 of 5 |
| llms.txt links to pages that do not load | 2 of 5 |
| The homepage is reached through a chain of redirects | 1 of 5 |
| The ARD manifest is valid but its entries will not be found by search | 1 of 5 |
| A missing agent file answers with a full page | 1 of 5 |
| A business record gives an address but no coordinates | 1 of 5 |
Section scores on this fetch
Weakest first. 12 of 25 scored sections at 90 or above.
| Section | Score |
|---|---|
| Payload and render path | 20 |
| Agent instruction surface | 50 |
| Authorship and trust signals (E-E-A-T proxies) | 57 |
| Quotable content | 57 |
| Machine layer | 67 |
| Naming and case consistency | 67 |
| Entity corroboration | 75 |
| Claim consistency | 75 |
| Schema and entity graph | 78 |
| Internal linking | 80 |
| Image signals | 80 |
| Sitemap coverage | 83 |
| Machine-file trust chain | 86 |
| Server and hosting | 100 |
| RDF and linked-data surface | 100 |
| Accessibility structure (from the delivered HTML) | 100 |
| Indexability | 100 |
| Crawl waste | 100 |
| Page subject, the Webref question | 100 |
| AI and search agents | 100 |
| Speed a crawler sees, and field data where it exists | 100 |
| What each agent receives | 100 |
| Mobile surface | 100 |
| Exposed files and secrets | 100 |
| Error pages | 100 |
Shelves
| Shelf | State | Definition |
|---|---|---|
| llms.txt | on the shelf | What counts, and who has it |
| agents.md | on the shelf | What counts, and who has it |
| Media kit | not found | What counts, and who has it |
| Entity graph | on the shelf | What counts, and who has it |
| AI access policy | on the shelf | What counts, and who has it |
| Agent-callable | on the shelf | What counts, and who has it |
Questions about palisade.email
Has the owner of palisade.email been verified?
Owner not verified. Nobody has proved to CrawlCheck that they run this site. Proving it is free and takes one DNS record or one meta tag.
Can AI assistants read palisade.email?
On 2026-11-16 it was graded C, 85 of 100, with 8 findings. It serves 5 of the 6 things the registry looks for: llms, agents, entity, aipolicy, agentapi.
How current is this page?
CrawlCheck last read palisade.email on 2026-11-16. The page changes only when a new read does.
The full report for this fetch
Machine-readable: /api/registry?host=palisade.email. This row states what was served to CrawlCheck at that time. It is not an endorsement, and it says nothing this scan did not measure.