Export Report
OVERALL SCORE
Level 4, Mostly Ready
- AI Discoverability 70 out of 100
- Agent Ease of Use 56 out of 100
- Security & Trust 95 out of 100
- GEO, AIO and AEO 68 out of 100
- SEO 100 out of 100
- Performance 98 out of 100
- Accessibility 96 out of 100
What AI sees of your website
IntoDNS.AI — Modern DNS & Email Security Scanner (SPF, DKIM, DMARC)
IntoDNS.AI — modern DNS & email security scanner. SPF, DKIM, DMARC, DNSSEC, MTA-STS, BIMI, FCrDNS, blacklists with AI-assisted fixes and a free public API. No signup. The modern alternative to the classic IntoDNS report.
Next step
Turn this report into a fix workflow
3 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 70 | Needs work | 36 | 7 | 2 | View details |
| Discoverability | 67 | Needs work | 8 | 2 | 0 | View details |
| Content Readiness | 81 | Mostly ready | 25 | 5 | 2 | View details |
| Bot Access Control | 63 | Needs work | 3 | 0 | 0 | |
| Agent Ease of Use | 56 | Needs work | 8 | 0 | 0 | |
| API | 80 | Mostly ready | 7 | 0 | 0 | |
| MCP | 43 | Priority fix | 1 | 0 | 0 | |
| GEO, AIO and AEO | 68 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 5 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 95 | Strong | 27 | 0 | 0 | |
| Security & Trust | 95 | Strong | 27 | 0 | 0 | |
| Performance | 98 | Strong | 16 | 0 | 0 | |
| Performance | 98 | Strong | 16 | 0 | 0 | |
| Accessibility | 96 | Strong | 6 | 0 | 0 | |
| Accessibility | 96 | Strong | 6 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
100 Fail
AI DiscoverabilityDiscoverabilityEstablished
Link headers
Link headers failed at "Find useful Link headers".
Needs attention
Link headers
Issue
No useful agent discovery Link headers were found.
Why it matters
Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.
Check name
Link headers
Score
0/100
Status
fail
Category
Discoverability
Maturity
Established
Goal
Include Link response headers for agent discovery using RFC 8288.
Result
Link headers failed at "Find useful Link headers".
Validation steps
Find useful Link headers
No useful agent discovery Link headers were found.
Fetch same-origin Link header targets
Link headers did not expose any same-origin targets to validate.
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
45 Fail
AI DiscoverabilityContent ReadinessEstablished
Markdown negotiation
Markdown negotiation is missing or incomplete.
Needs attention
Markdown negotiation
Issue
Best candidate returned Content-Type "text/html; charset=utf-8" instead of text/markdown.
Why it matters
Markdown representations give agents a cleaner page form while preserving normal HTML for browsers and cache-safe representation handling.
Check name
Markdown negotiation
Score
10/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose a useful Markdown representation through negotiation or an explicit alternate URL.
Result
Markdown negotiation is missing or incomplete.
Validation steps
Markdown representation
No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.
Same-URL negotiation
Same-URL Accept: text/markdown did not return a valid Markdown representation.
Markdown format validation
Markdown response contains too much raw HTML to be a clean agent-facing Markdown representation.
Advertised Markdown alternate
No Link or HTML rel=alternate text/markdown URL was advertised.
Conventional .md mirror
Conventional .md mirror candidates did not return valid Markdown.
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Score llms.txt structure and usefulness".
17 Fail
AI DiscoverabilityContent ReadinessEmerging recommendation
llms.txt
llms.txt failed at "Score llms.txt structure and usefulness".
Needs attention
llms.txt
Issue
llms.txt includes unsafe or private links that should not be advertised to agents.
Details
Why it matters
llms.txt is an emerging Markdown convention for giving language-model clients curated context and links before they crawl broadly. Broken, private, or low-signal links make the file much less useful even when it exists.
Check name
llms.txt
Score
66/100
Status
fail
Category
Content Readiness
Maturity
Emerging recommendation
Goal
Publish a concise llms.txt index that helps agents discover useful public site context.
Result
llms.txt failed at "Score llms.txt structure and usefulness".
Validation steps
Score llms.txt structure and usefulness
llms.txt includes unsafe or private links that should not be advertised to agents.
Findings
- Missing a blockquote summary. The llms.txt proposal recommends a concise blockquote after the H1.
- No Markdown-formatted links were found.
- Several links have vague labels or raw URL labels.
- 1 links point to private, internal, credentialed, or non-HTTP(S) targets.
Probe sampled linked resources
Some sampled llms.txt links were broken, redirected unexpectedly, or did not return clearly agent-readable content.
Findings
- 3/25 probed links were broken or unreachable.
- 3/25 probed links did not look agent-readable.
Inspect optional llms-full.txt
Passed.
Sign in to see 26 other issues and the full report
Create a free account to unlock every issue, evidence details, exports, and higher free limits.
Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history