Website check complete
2 important improvements deserve attention.
Checked Sep 16, 2026 · 52 public signals · light scan · methodology 2026.09.1Start here
Use a main landmark and sequential headings so browsers, assistive technology, and agents can understand the page outline.
main present; max heading skip 2The overview
About, contact, privacy, and terms pages let visitors verify who operates the product.
about: no · privacy: no · terms: no · contact: noTell agents which jobs the product is appropriate for and where to begin.
No explicit guidance detectedDMARC quarantine or reject policies reduce spoofing once mail sources are aligned.
p=none · reporting yesUse one H1 and avoid skipping heading levels so readers and agents can follow the document outline.
H1 1 · H2 7 · H3 2 · max skip 2Summarize the product, audience, and value clearly for search and link previews.
341 charactersInteractive elements need a text or ARIA-derived name.
9/9 statically nameableSemantic landmarks make the page structure understandable without visual layout.
3/4 common landmarks; main presentThe homepage is requested with common crawler and user-fetch agent identifiers.
3/3 user-agents received readable contentDeclare the preferred public URL so crawlers consolidate duplicate variants.
https://bountyhunt.xyz/Meaningful copy should be available without JavaScript execution.
744 words · 4948 characters · 6.6% content ratioDeclare the content language with a valid html lang attribute.
enA missing page should give a reader a recovery path such as home, docs, search, or sitemap.
353 readable charactersThe public homepage should not accidentally declare noindex.
No noindex directiveThe public product should finish on an encrypted HTTPS origin.
https://bountyhunt.xyzA useful llms.txt provides a concise product summary and links to canonical resources.
1406 characters · 7 linksLinks declared for agents should resolve to real public content.
2/2 sampled links healthyUse a title, summary, and described sections so the file works as a navigation index.
title yes · summary yes · sections yesUnbalanced code fences can hide the remainder of a Markdown document from parsers.
BalancedCanonical URL, language, Open Graph image, and Open Graph type improve attribution and previews.
canonical yes · lang en · og:image yes · og:type websiteHTTPS pages should not reference insecure HTTP assets.
None detectedA responsive viewport lets the page render at the correct width on mobile devices.
width=device-width, initial-scale=1.0Prefer native links, buttons, and form controls over clickable generic elements.
1 native · 0 non-native patternsThe public homepage should not require a challenge or sign-in before its content can be read.
No challenge/login language detectedProducts using delegated authorization should publish standard discovery metadata.
authorization server valid · protected resource validProvide a title, description, type, and image for reliable launch-link previews.
title/description yes · image yesKeep extracted page content within a practical agent context budget.
2 pages sampled · largest 4,948 charactersUse a concise, specific title that identifies the product and page.
54 characters · BountyHunt — Live Bug Bounty Commit Alerts & DashboardMake the next step explicit with clear action language and a valid destination.
Action language detectedUse HTTP redirects and avoid meta-refresh or JavaScript-only redirect stubs.
0 HTTP redirect(s)Crawler policies should intentionally distinguish training, search indexing, and user-requested retrieval.
ChatGPT-User: allowed · GPTBot: allowed · ClaudeBot: allowed · Claude-User: allowed · PerplexityBot: allowed · Google-Extended: allowedEvaluate CSP scope and HSTS duration instead of header presence alone.
CSP 11 directives · wildcard no · HSTS 15552000sAccurate lastmod values help crawlers prioritize changed pages.
98% of entries include lastmodPublish a valid sitemap or sitemap index for canonical public URLs.
476 locationsA valid SPF policy helps recipients identify authorized senders; excessive DNS lookups can invalidate it.
~all · 1 lookup mechanism(s)Use relevant JSON-LD types with enough identity fields to resolve the organization or product.
Organization, WebSite, SoftwareApplication, Offer · organization fields: name, url, logoPublic pages should expose substantive content without a login or challenge wall.
2/2 sampled pagesMissing pages should return 404 or 410 instead of a successful app shell.
HTTP 404Products offering an A2A agent can publish a machine-readable agent card.
Not discoveredProducts with authentication can expose concise public setup and recovery guidance in auth.md.
Not discoveredEmerging catalogs can advertise APIs, agents, skills, and MCP surfaces from a well-known location.
ARD not found · API catalog not foundA published Agent Skills index should be valid JSON and enumerate usable skill artifacts.
Not discoveredProducts with developer interfaces should expose a predictable developer entry point.
Not discoveredA contact address on the product domain can strengthen operator identity and support trust.
Not observedInputs, selects, and textareas should have associated labels.
No visible form controlsAdvertise a Markdown representation through content negotiation or an alternate link.
Not advertisedCanonical pages can optionally serve Markdown when requested and must vary caches by Accept.
HTML served for a Markdown requestA server card lets clients understand an MCP server before connecting.
Not discoveredProducts with a public API should publish a machine-readable OpenAPI document.
Not discoveredProducts with public pricing should make it easy to find from the homepage.
Not discoveredLink public documentation from a page visitors and agents already reach.
Not discoveredA security.txt file gives researchers a supported disclosure route.
Not foundsameAs links help disambiguate the brand across authoritative profiles.
0 sameAs link(s)