Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 72 out of 100
- Agent Ease of Use 56 out of 100
- Security & Trust 86 out of 100
- GEO, AIO and AEO 72 out of 100
- SEO 92 out of 100
- Performance 54 out of 100
- Accessibility 29 out of 100
What AI sees of your website
Gizmodo | The Future Is Here
Dive into cutting-edge tech, reviews and the latest trends with the expert team at Gizmodo. Your ultimate source for all things tech.
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.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 72 | Needs work | 37 | 0 | 0 | |
| Discoverability | 67 | Needs work | 8 | 0 | 0 | |
| Content Readiness | 73 | Needs work | 23 | 0 | 0 | |
| Bot Access Control | 75 | Mostly ready | 6 | 0 | 0 | |
| Agent Ease of Use | 56 | Needs work | 3 | 1 | 0 | View details |
| API | 67 | Needs work | 1 | 0 | 0 | |
| Skill Discovery | 55 | Needs work | 2 | 1 | 0 | View details |
| GEO, AIO and AEO | 72 | Needs work | 11 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 4 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| SEO | 92 | Strong | 9 | 0 | 0 | |
| Security & Trust | 86 | Mostly ready | 23 | 2 | 2 | View details |
| Security & Trust | 86 | Mostly ready | 23 | 2 | 2 | View details |
| Performance | 54 | Needs work | 10 | 1 | 0 | View details |
| Performance | 54 | Needs work | 10 | 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 "Evaluate fetch baseline".
50 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate fetch baseline".
Needs attention
Content-Security-Policy
Issue
CSP does not define default-src; several fetch directives may have no restrictive fallback.
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
50/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.
Result
Content-Security-Policy failed at "Evaluate fetch baseline".
Validation steps
Evaluate fetch baseline
CSP does not define default-src; several fetch directives may have no restrictive fallback.
Evaluate script execution
No script-src or default-src directive constrains script execution.
Review hardening directives
CSP is missing recommended hardening directives: object-src, base-uri, form-action.
Review CSP reporting
CSP does not define a reporting endpoint.
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=[]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives frameAncestors=["'self'"] formCount=2WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".
29 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
DNS-AID Agent Discovery
DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".
Needs attention
DNS-AID Agent Discovery
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
71/100
Status
fail
Category
Skill Discovery
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.gizmodo.com", "rrtype": "HTTPS", "ttl": 60, "mode": "unknown", "targetName": "108", "params": [ { "key": "00", "value": "present" }, { "key": "01", "value": "present" }, { "key": "00", "value": "present" }, { "key": "00", "value": "present" }, { "truncated": true, "omittedCount": 104, "originalCount": 108 } ], "mandatory": [], "alpn": [], "endpointIssue": "missing endpoint", "unknownParams": [ "00", "01", "00", "00", { "truncated": true, "omittedCount": 104, "originalCount": 108 } ], "parseWarnings": [ "SvcPriority is missing or not numeric." ], "source": "cloudflare-doh-json", "raw": "\\# 108 00 01 00 00 01 00 06 02 68 33 02 68 32 00 05 00 47 00 45 fe 0d 00 41 28 00 20 00 20 f7 d6 d6 38 44 8d b7 c6 14 d6 2b e4 06 6e 79 39 ba 19 3b f0 a8 1d 1c 09 de 0d ca ab ae 03 32 11 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 10 26 06 47 00 97 69 58 b1 5b 76 00 00 07 ea 3d b7" }, { "ownerName": "_a2a._agents.gizmodo.com", "rrtype": "HTTPS", "ttl": 60, "mode": "unknown", "targetName": "108", "params": [ { "key": "00", "value": "present" }, { "key": "01", "value": "present" }, { "key": "00", "value": "present" }, { "key": "00", "value": "present" }, { "truncated": true, "omittedCount": 104, "originalCount": 108 } ], "mandatory": [], "alpn": [], "endpointIssue": "missing endpoint", "unknownParams": [ "00", "01", "00", "00", { "truncated": true, "omittedCount": 104, "originalCount": 108 } ], "parseWarnings": [ "SvcPriority is missing or not numeric." ], "source": "cloudflare-doh-json", "raw": "\\# 108 00 01 00 00 01 00 06 02 68 33 02 68 32 00 05 00 47 00 45 fe 0d 00 41 28 00 20 00 20 f7 d6 d6 38 44 8d b7 c6 14 d6 2b e4 06 6e 79 39 ba 19 3b f0 a8 1d 1c 09 de 0d ca ab ae 03 32 11 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 10 26 06 47 00 97 69 58 b1 5b 76 00 00 07 ea 3d b7" } ]
Evidence log1 step · 6 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.gizmodo.com" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILDNS-AID record has parse/shape warnings ownerName="_a2a._agents.gizmodo.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.PerformancePerformanceBrowser audit
Document request latency
100 Fail
PerformancePerformanceBrowser audit
Document request latency
Check name
Document request latency
Score
0/100
Status
fail
Device
desktop
Category
Performance
Estimated savings
Est savings of 510 ms
Fix guidance
Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression.
References
https://web.dev/learn/performance/Evidence
{
"displayValue": "Est savings of 510 ms",
"description": "Your first network request is the most important. [Reduce its latency](https://developer.chrome.com/docs/performance/insights/document-latency) by avoiding redirects, ensuring a fast server response, and enabling text compression."
}Sign in to see 40 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.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 63/100 | Level 3, Bot-Aware | Current report | |
| 64/100 | Level 3, Bot-Aware | View report |