Results for https://www.veri-doc.tech/ LEVEL 0 Scanned just now
14 /100
Not Ready
Discoverability
25
1 pass · 3 fail
Content Accessibility
0
0 pass · 1 fail
Bot Access Control
50
1 pass · 1 fail
Discovery
0
0 pass · 7 fail
Commerce
—
1 pass · 0 fail
01 / 04 pass
Discoverability
- fetch GET /robots.txt 200
User-agent: Googlebot Allow: / User-agent: Bingbot Allow: / User-agent: Twitterbot Allow: / User-agent: facebookexternalhit Allow: / User-agent: * Allow: /
- conclude robots.txt present with User-agent directive
{"contentType":"text/plain; charset=utf-8"}
- fetch GET /sitemap.xml 200
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>VeriDoc - Document Verification Platform</title> <meta name="description" content="Verify document authenticity using blockchain-based verification. Upload files to generate ZK Proofs and check their verification status on-chain." /> <meta name="author" content="Vedant Anand" /> <meta name="keywords" content="Document Verification, … - fetch GET /sitemap_index.xml 200
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>VeriDoc - Document Verification Platform</title> <meta name="description" content="Verify document authenticity using blockchain-based verification. Upload files to generate ZK Proofs and check their verification status on-chain." /> <meta name="author" content="Vedant Anand" /> <meta name="keywords" content="Document Verification, … - conclude No valid XML sitemap found
- fetch GET / 200
- conclude No Link header on homepage
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- dns AD=false status=3 answers=0
- conclude No DNSSEC-validated (AD=true) ServiceMode DNS-AID records
00 / 01 pass
Content Accessibility
- fetch GET / 200
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>VeriDoc - Document Verification Platform</title> <meta name="description" content="Verify document authenticity using blockchain-based verification. Upload files to generate ZK Proofs and check their verification status on-chain." /> <meta name="author" content="Vedant Anand" /> <meta name="keywords" content="Document Verification, … - conclude No markdown negotiation (content-type=text/html; charset=utf-8)
{"status":200,"contentType":"text/html; charset=utf-8"}
01 / 03 pass
Bot Access Control
- parse Parsed 5 user-agent group(s)
- conclude Found AI crawler rules or User-agent: * policy
- parse Content-Signal lines: 0
- conclude No Content-Signal directives with ai-train/search/ai-input
- fetch GET /.well-known/http-message-signatures-directory 404
{"error": {"code": "404", "message": "The page could not be found"}} - conclude Directory missing or invalid — reporting neutral
{"status":404}
00 / 08 pass
Discovery
- fetch GET /.well-known/api-catalog 404
{"error": {"code": "404", "message": "The page could not be found"}} - conclude HTTP 404
- fetch GET /.well-known/openid-configuration 404
{"error": {"code": "404", "message": "The page could not be found"}} - fetch GET /.well-known/oauth-authorization-server 404
{"error": {"code": "404", "message": "The page could not be found"}} - conclude No valid OAuth/OIDC discovery document
- fetch GET /.well-known/oauth-protected-resource 404
{"error": {"code": "404", "message": "The page could not be found"}} - conclude PRM missing or incomplete
- fetch GET /auth.md 200
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>VeriDoc - Document Verification Platform</title> <meta name="description" content="Verify document authenticity using blockchain-based verification. Upload files to generate ZK Proofs and check their verification status on-chain." /> <meta name="author" content="Vedant Anand" /> <meta name="keywords" content="Document Verification, … - fetch GET /.well-known/oauth-protected-resource 404
{"error": {"code": "404", "message": "The page could not be found"}} - parse authMd=false prm=false agent_auth=false registrationDocs=false
- conclude auth.md discovery incomplete
{"authOk":false,"prmOk":false,"agentAuth":false,"mentionsRegistration":false}
- fetch GET /.well-known/mcp.json 404
{"error": {"code": "404", "message": "The page could not be found"}} - fetch GET /.well-known/mcp/server-cards.json 404
{"error": {"code": "404", "message": "The page could not be found"}} - fetch GET /.well-known/mcp/server-card.json 404
{"error": {"code": "404", "message": "The page could not be found"}} - fetch POST /api/mcp/mcp 405
- conclude No MCP card or live endpoint
- conclude Check disabled for this scan
- fetch GET /.well-known/agent-skills/index.json 404
{"error": {"code": "404", "message": "The page could not be found"}} - fetch GET /.well-known/skills/index.json 404
{"error": {"code": "404", "message": "The page could not be found"}} - conclude No valid agent-skills index
- fetch Launching Browser Rendering session for WebMCP inspection
- parse Captured 0 WebMCP tool registration(s)
- conclude No tools recorded via provideContext/registerTool
01 / 05 pass
Commerce
- conclude Coinbase Bazaar discovery not queried (skipped in v1 scanner)
- fetch GET / 200
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>VeriDoc - Document Verification Platform</title> <meta name="description" content="Verify document authenticity using blockchain-based verification. Upload files to generate ZK Proofs and check their verification status on-chain." /> <meta name="author" content="Vedant Anand" /> <meta name="keywords" content="Document Verification, … - fetch GET /api 200
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>VeriDoc - Document Verification Platform</title> <meta name="description" content="Verify document authenticity using blockchain-based verification. Upload files to generate ZK Proofs and check their verification status on-chain." /> <meta name="author" content="Vedant Anand" /> <meta name="keywords" content="Document Verification, … - fetch GET /api/v1 200
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>VeriDoc - Document Verification Platform</title> <meta name="description" content="Verify document authenticity using blockchain-based verification. Upload files to generate ZK Proofs and check their verification status on-chain." /> <meta name="author" content="Vedant Anand" /> <meta name="keywords" content="Document Verification, … - conclude No 402 x402 challenge found
- fetch GET /openapi.json 200
{ "openapi": "3.1.0", "info": { "title": "VeriDoc Document Verify", "description": "VeriDoc verifies document authenticity on Ethereum Sepolia. Hash a file with keccak-256 and check whether that hash was previously registered on the VeriDoc smart contract — the file itself is never uploaded. Use for certificates, contracts, transcripts, and any registered document. Speaks x402: $0.05 USDC per call on Base, no account or API key. Paywalled URL: https://www.getbags.app/api/agent/link/p… - parse x-payment-info present=true
- conclude MPP extensions found
- fetch GET /.well-known/ucp 404
{"error": {"code": "404", "message": "The page could not be found"}} - conclude HTTP 404
- fetch GET /.well-known/acp.json 404
{"error": {"code": "404", "message": "The page could not be found"}} - conclude HTTP 404
- conclude Check disabled for this scan
Improve the score
Next: Level 1 — Basic Web Presence
Expose a valid XML sitemap (via robots.txt Sitemap: or /sitemap.xml)
Advertise agent-useful Link relations on the homepage
Next level
Level 1 — Basic Web Presence