CanAgentUse

Saved report

https://kriesi.at/

SCANNED

Jun 25, 2026, 3:05 PM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

New Scan

https://kriesi.at/

SCANNED

Jun 25, 2026, 3:05:21 PMJun 25, 2026, 3:05 PM

VISIBILITY

Public

SUITE2026.06.10

Rescan Report

Share Report

Copy Report Link

Export Report

59/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents

CAPTURED SCREENSHOT

What AI sees of your website

Home - Kriesi.at - Premium WordPress Themes

Get sleek premium Wordpress Themes and read tutorials on Wordpress, HTML, CSS and jQuery.

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.

Detailed report scores grouped by capability area
Metric	Score	Status	Passed	Failed	Warning	Evidence
AI Discoverability	69	Needs work	30	0	0
Discoverability	67	Needs work	8	0	0
Content Readiness	72	Needs work	18	0	0
Bot Access Control	69	Needs work	4	0	0
Agent Ease of Use	47	Priority fix	2	4	1	View details
Auth	37	Priority fix	1	3	0	View details
Skill Discovery	53	Needs work	1	1	1	View details
GEO, AIO and AEO	57	Needs work	6	0	0
GEO Readiness	Not Applicable	Not Applicable	1	0	0
AIO Readiness	Not Applicable	Not Applicable	3	0	0
AEO Readiness	Not Applicable	Not Applicable	2	0	0
SEO	100	Strong	10	0	0
SEO	100	Strong	10	0	0
Security & Trust	46	Priority fix	8	1	0	View details
Security & Trust	46	Priority fix	8	1	0	View details
Performance	76	Mostly ready	12	0	0
Performance	76	Mostly ready	12	0	0

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

90 Fail

Needs attention

Auth.md Agent Registration

Failed check

Issue

auth.md could not be fetched.

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

10/100

Status

fail

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

Validation steps

Fetch and validate /auth.md
auth.md could not be fetched.
Validate protected resource metadata
OAuth Protected Resource Metadata could not be fetched.
Validate Auth.md authorization metadata
OAuth authorization-server metadata could not be fetched.

Evidence log3 steps · 18 lines

Fetch and validate /auth.md [fail]! auth.md could not be fetched.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=404 contentType="text/html; charset=UTF-8" bytes=44339FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="auth.md could not be fetched."FAILauth.md could not be fetched.Validate protected resource metadata [fail]! OAuth Protected Resource Metadata could not be fetched.INFOValidate protected resource metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-protected-resource" statusCode=404 contentType="text/html; charset=UTF-8" bytes=43387FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth Protected Resource Metadata could not be fetched."FAILOAuth Protected Resource Metadata could not be fetched.Validate Auth.md authorization metadata [fail]! OAuth authorization-server metadata could not be fetched.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=404 contentType="text/html; charset=UTF-8" bytes=43403FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth authorization-server metadata could not be fetched."FAILOAuth authorization-server metadata could not be fetched.

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.

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.

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.

Malformed record issues

[
  {
    "ownerName": "_index._agents.kriesi.at",
    "rrtype": "HTTPS",
    "ttl": 300,
    "mode": "unknown",
    "targetName": "136",
    "params": [
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "01",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "truncated": true,
        "omittedCount": 132,
        "originalCount": 136
      }
    ],
    "mandatory": [],
    "alpn": [],
    "endpointIssue": "missing endpoint",
    "unknownParams": [
      "00",
      "01",
      "00",
      "00",
      {
        "truncated": true,
        "omittedCount": 132,
        "originalCount": 136
      }
    ],
    "parseWarnings": [
      "SvcPriority is missing or not numeric."
    ],
    "source": "cloudflare-doh-json",
    "raw": "\\# 136 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 08 68 15 09 e4 ac 43 a1 61 00 05 00 47 00 45 fe 0d 00 41 6b 00 20 00 20 7f 95 2f 84 55 02 33 14 bd 44 d4 79 df 30 6e 97 8b fc bd 50 6b 78 5e a7 4c f5 92 3a 09 95 74 7c 00 04 00 01 00 01 00 12 63 6c 6f 75 64 66 6c 61 72 65 2d 65 63 68 2e 63 6f 6d 00 00 00 06 00 20 26 06 47 00 30 30 00 00 00 00 00 00 ac 43 a1 61 26 06 47 00 30 36 00 00 00 00 00 00 68 15 09 e4"
  },
  {
    "ownerName": "_a2a._agents.kriesi.at",
    "rrtype": "HTTPS",
    "ttl": 300,
    "mode": "unknown",
    "targetName": "136",
    "params": [
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "01",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "key": "00",
        "value": "present"
      },
      {
        "truncated": true,
        "omittedCount": 132,
        "originalCount": 136
      }
    ],
    "mandatory": [],
    "alpn": [],
    "endpointIssue": "missing endpoint",
    "unknownParams": [
      "00",
      "01",
      "00",
      "00",
      {
        "truncated": true,
        "omittedCount": 132,
        "originalCount": 136
      }
    ],
    "parseWarnings": [
      "SvcPriority is missing or not numeric."
    ],
    "source": "cloudflare-doh-json",
    "raw": "\\# 136 00 01 00 00 01 00 06 02 68 33 02 68 32 00 04 00 08 68 15 09 e4 ac 43 a1 61 00 05 00 47 00 45 fe 0d 00 41 6b 00 20 00 20 7f 95 2f 84 55 02 33 14 bd 44 d4 79 df 30 6e 97 8b fc bd 50 6b 78 5e a7 4c f5 92 3a 09 95 74 7c 00 04 00 01 00 01 00 12 63 6c 6f 75 64 66 6c 61 72 65 2d 65 63 68 2e 63 6f 6d 00 00 00 06 00 20 26 06 47 00 30 30 00 00 00 00 00 00 ac 43 a1 61 26 06 47 00 30 36 00 00 00 00 00 00 68 15 09 e4"
  }
]

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

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

Sign in to see 38 other issues and the full report

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

Development Note:

Please configure GOOGLE_CLIENT_ID in .env to activate live login.

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

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
Jun 25, 2026	59/100	Level 3, Bot-Aware	Current report

Level 3, Bot-Aware

CAPTURED SCREENSHOT

What AI sees of your website

Home - Kriesi.at - Premium WordPress Themes

Turn this report into a fix workflow

Issues ranked by score impact

Auth.md Agent Registration

Auth.md Agent Registration

Issue

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

Content-Security-Policy

Content-Security-Policy

Issue

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

DNS-AID Agent Discovery

DNS-AID Agent Discovery

Issue

Details

Why it matters

Check name

Score

Status

Category

Maturity

Goal

Result

Validation steps

Malformed record issues

Sign in to see 38 other issues and the full report

Fix with MCP or CLI

Public scan score over time