CanAgentUse

Make your website ready for AI agents.

CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

UCP Validator UCP Playground

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

MCP Playground

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

A2A Playground

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

Agent Website Viewer

https://exif.tools/

SCANNED

Jul 28, 2026, 3:10 PM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

New Scan

https://exif.tools/

SCANNED

Jul 28, 2026, 3:10 PM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

Export Report

58/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents

CAPTURED SCREENSHOT

What AI sees of your website

EXIFTool Online: EXIF & Metadata Viewer | exif.tools

Use this online metadata viewer to check EXIF data, GPS, XMP, IPTC, ICC, hashes, and magic bytes. Files stay private and are analyzed in your browser.

Open Agent View

Next step

Turn this report into a fix workflow

2 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.

Fix with MCP / CLI

Detailed report scores grouped by capability area
Metric	Score	Status	Passed	Failed	Warning	Evidence
AI Discoverability	56	Needs work	28	1	0	View details
Discoverability	67	Needs work	8	0	0
Content Readiness	59	Needs work	19	0	0
Bot Access Control	45	Priority fix	1	1	0	View details
Agent Ease of Use	55	Needs work	3	1	1	View details
Skill Discovery	53	Needs work	1	1	1	View details
Google Agentic Browsing	67	Needs work	2	0	0
GEO, AIO and AEO	64	Needs work	11	0	0
GEO Readiness	Not Applicable	Not Applicable	3	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	26	0	0
Security & Trust	95	Strong	26	0	0
Performance	100	Strong	22	0	0
Performance	100	Strong	22	0	0
Accessibility	0	Priority fix	0	1	0	View details
Accessibility	0	Priority fix	0	1	0	View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

69 Fail

Needs attention

AI bot rules in robots.txt

Failed check

Issue

No explicit User-agent rules were found for major AI crawler tokens.

Details

Why it matters

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Maturity

Established

Goal

Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.

Result

AI bot rules in robots.txt failed at "Classify AI crawler rules".

Validation steps

Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
robots.txt lacks explicit AI crawler rules

Evidence log1 step · 6 lines

Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".

39 Fail

Needs attention

DNS-AID Agent Discovery

Failed check

Issue

One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

Details

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.

Check name

DNS-AID Agent Discovery

Score

61/100

Status

fail

Maturity

Emerging recommendation

Goal

Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".

Validation steps

Validate HTTPS/SVCB shape

One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

DNS-AID HTTPS/SVCB records are malformed

Malformed record issues

[
  {
    "ownerName": "_index._agents.exif.tools",
    "rrtype": "HTTPS",
    "ttl": 300,
    "mode": "unknown",
    "targetName": "81",
    "params": [
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "01",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "truncated": true,
        "omittedCount": 77,
        "originalCount": 81
      }
    ],
    "mandatory": [],
    "alpn": [],
    "endpointIssue": "missing endpoint",
    "unknownParams": [
      "00",
      "01",
      "00",
      "00",
      {
        "truncated": true,
        "omittedCount": 77,
        "originalCount": 81
      }
    ],
    "parseWarnings": [
      "SvcPriority is missing or not numeric."
    ],
    "source": "cloudflare-doh-json",
    "raw": "\\# 81 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 0c 68 1a 00 13 68 1a 01 13 ac 43 44 b1 00 06 00 30 26 06 47 00 00 20 00 00 00 00 00 00 68 1a 00 13 26 06 47 00 00 20 00 00 00 00 00 00 68 1a 01 13 26 06 47 00 00 20 00 00 00 00 00 00 ac 43 44 b1"
  },
  {
    "ownerName": "_a2a._agents.exif.tools",
    "rrtype": "HTTPS",
    "ttl": 300,
    "mode": "unknown",
    "targetName": "81",
    "params": [
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "01",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "truncated": true,
        "omittedCount": 77,
        "originalCount": 81
      }
    ],
    "mandatory": [],
    "alpn": [],
    "endpointIssue": "missing endpoint",
    "unknownParams": [
      "00",
      "01",
      "00",
      "00",
      {
        "truncated": true,
        "omittedCount": 77,
        "originalCount": 81
      }
    ],
    "parseWarnings": [
      "SvcPriority is missing or not numeric."
    ],
    "source": "cloudflare-doh-json",
    "raw": "\\# 81 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 0c 68 1a 00 13 68 1a 01 13 ac 43 44 b1 00 06 00 30 26 06 47 00 00 20 00 00 00 00 00 00 68 1a 00 13 26 06 47 00 00 20 00 00 00 00 00 00 68 1a 01 13 26 06 47 00 00 20 00 00 00 00 00 00 ac 43 44 b1"
  }
]

Check DNSSEC authentication evidence
DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.
DNSSEC authentication evidence is missing

Evidence log2 steps · 17 lines

Validate HTTPS/SVCB shape [fail]! One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.INFOValidate HTTPS/SVCB shapeFAILCompare parsed DNS-AID record count actual=2 expected="> 0"FAILCompare ServiceMode record count actual=0 expected="> 0"FAILDNS-AID record has parse/shape warnings ownerName="_index._agents.exif.tools" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILDNS-AID record has parse/shape warnings ownerName="_a2a._agents.exif.tools" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILOne or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.Check DNSSEC authentication evidence [warning]! DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=false expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.exif.tools" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.exif.tools" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.exif.tools" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.exif.tools" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.exif.tools" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.exif.tools" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="exif.tools" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

References

www.deque.com/accessibility/core-documentation Browser agent UX guide for forms and modals

Evidence

{
  "error": "Accessibility audit did not return a result."
}

Sign in to see 23 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.

Fix with MCP / CLI

Score history

Want help fixing this?

Level 3, Bot-Aware

CAPTURED SCREENSHOT

What AI sees of your website

EXIFTool Online: EXIF & Metadata Viewer | exif.tools

Turn this report into a fix workflow

Issues ranked by score impact

AI bot rules in robots.txt

AI bot rules in robots.txt

Issue

Details

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

robots.txt lacks explicit AI crawler rules

DNS-AID Agent Discovery

DNS-AID Agent Discovery

Issue

Details

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

DNS-AID HTTPS/SVCB records are malformed

Malformed record issues

DNSSEC authentication evidence is missing

Accessibility audit

Check name

Score

Status

Device

Category

Fix guidance

References

Sign in to see 23 other issues and the full report

Fix with MCP or CLI