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://www.learnitlive.com/

SCANNED

Jul 10, 2026, 5:25 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

New Scan

https://www.learnitlive.com/

SCANNED

Jul 10, 2026, 5:25 AM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

Export Report

63/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents

CAPTURED SCREENSHOT

What AI sees of your website

Learn with Real Experts Around the World | Learn It Live

Join live and on-demand expert-led classes across wellness, spirituality, relationships, parenting, personal growth, career, and more on Learn It Live.

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	66	Needs work	25	0	0
Discoverability	67	Needs work	8	0	0
Content Readiness	68	Needs work	14	0	0
Bot Access Control	63	Needs work	3	0	0
Agent Ease of Use	59	Needs work	4	1	1	View details
Auth	48	Priority fix	1	0	0
Skill Discovery	53	Needs work	1	1	1	View details
Google Agentic Browsing	100	Strong	2	0	0
GEO, AIO and AEO	50	Needs work	6	0	0
GEO Readiness	Not Applicable	Not Applicable	2	0	0
AIO Readiness	Not Applicable	Not Applicable	3	0	0
AEO Readiness	Not Applicable	Not Applicable	1	0	0
SEO	100	Strong	10	0	0
SEO	100	Strong	10	0	0
Security & Trust	64	Needs work	14	1	0	View details
Security & Trust	64	Needs work	14	1	0	View details
Performance	85	Mostly ready	14	1	0	View details
Performance	85	Mostly ready	14	1	0	View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

60 Fail

Needs attention

Content-Security-Policy

Failed check

Issue

Applicable HTML response is missing an enforcing Content-Security-Policy header.

Details

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

40/100

Status

fail

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Find enforcing CSP delivery".

Validation steps

Find enforcing CSP delivery
Applicable HTML response is missing an enforcing Content-Security-Policy header.
Enforcing Content-Security-Policy header is missing

Evidence log1 step · 4 lines

Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.

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.www.learnitlive.com",
    "rrtype": "HTTPS",
    "ttl": 60,
    "mode": "unknown",
    "targetName": "33",
    "params": [
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "01",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "truncated": true,
        "omittedCount": 29,
        "originalCount": 33
      }
    ],
    "mandatory": [],
    "alpn": [],
    "endpointIssue": "missing endpoint",
    "unknownParams": [
      "00",
      "01",
      "00",
      "00",
      {
        "truncated": true,
        "omittedCount": 29,
        "originalCount": 33
      }
    ],
    "parseWarnings": [
      "SvcPriority is missing or not numeric."
    ],
    "source": "cloudflare-doh-json",
    "raw": "\\# 33 00 01 00 00 01 00 06 02 68 33 02 68 32 00 06 00 10 26 06 47 00 83 b2 b8 62 79 76 00 00 08 af 1d 00"
  },
  {
    "ownerName": "_a2a._agents.www.learnitlive.com",
    "rrtype": "HTTPS",
    "ttl": 60,
    "mode": "unknown",
    "targetName": "33",
    "params": [
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "01",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "truncated": true,
        "omittedCount": 29,
        "originalCount": 33
      }
    ],
    "mandatory": [],
    "alpn": [],
    "endpointIssue": "missing endpoint",
    "unknownParams": [
      "00",
      "01",
      "00",
      "00",
      {
        "truncated": true,
        "omittedCount": 29,
        "originalCount": 33
      }
    ],
    "parseWarnings": [
      "SvcPriority is missing or not numeric."
    ],
    "source": "cloudflare-doh-json",
    "raw": "\\# 33 00 01 00 00 01 00 06 02 68 33 02 68 32 00 06 00 10 26 06 47 00 90 d2 b8 62 79 76 00 00 08 af 1d 00"
  }
]

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 · 18 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.www.learnitlive.com" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILDNS-AID record has parse/shape warnings ownerName="_a2a._agents.www.learnitlive.com" 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.www.learnitlive.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.learnitlive.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.learnitlive.com" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.learnitlive.com" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.www.learnitlive.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.www.learnitlive.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="www.learnitlive.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="learnitlive.com" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

PerformancePerformanceBrowser audit

Forced reflow

100 Fail

Check name

Forced reflow

Score

0/100

Status

fail

Device

desktop

Fix guidance

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.

References

web.dev/learn/performance

Evidence

{
  "description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}

Sign in to see 33 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

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

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports

Public score history report links
Scan date	Score	Readiness	Report
Jul 10, 2026	63/100	Level 3, Bot-Aware	Current report

Want help fixing this?

Level 3, Bot-Aware

CAPTURED SCREENSHOT

What AI sees of your website

Learn with Real Experts Around the World | Learn It Live

Turn this report into a fix workflow

Issues ranked by score impact

Content-Security-Policy

Content-Security-Policy

Issue

Details

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

Enforcing Content-Security-Policy header is missing

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

Forced reflow

Check name

Score

Status

Device

Category

Fix guidance

References

Sign in to see 33 other issues and the full report

Fix with MCP or CLI

Public scan score over time