#llmsmap.me

Independent technical audit

snyfer.com

snyfer.com

Overall AI readiness score

A combined result across all audit signals.

91of 100Excellent
AI readiness audit: 10/30/2026Public technical data

About the site

Snyfer is an automated website forensics and threat intelligence service. It scans sites, collects technical signals, shared infrastructure links and regulatory warnings, and publishes reports with a Trust Score. The site offers domain scanning, API access, the Snyfer Shield browser extension and methodology documentation.

Platform:
Nuxt

Written by AI from the site’s llms.txt and homepage.

Overall AI readiness assessment

How ready snyfer.com is for AI systems

91/100

Snyfer was independently audited by llmsmap. snyfer.com currently scores 91/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.

Audit context

llms.txt is accessible and contains 778 tokens. An expanded llms-full.txt is also available with 3,072 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. The homepage exposes Schema.org types WebSite, Organization, SiteNavigationElement, SoftwareApplication, Dataset; 10 OpenGraph tags were found and markup completeness is 90%.

The mobile Lighthouse profile adds Performance 99/100, Accessibility 94/100, Best Practices 100/100, SEO 100/100, and experimental Agentic Browsing 67/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

  • Accessible llms.txt
  • Expanded llms-full.txt
  • 1 sitemap declaration
  • Schema.org: WebSite, Organization
  • Complete social metadata

Priority improvements

  1. 1Keep machine-readable files and markup aligned with future site changes.
llms.txt tokens778
llms-full.txt tokens3,072
ai.txt
sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse
99

Performance

94

Accessibility

100

Best Practices

100

Technical SEO

67

Agentic Browsing

What these results mean

The mobile page renders efficiently; its largest visible content block appeared in 1.2 s.

Accessibility scored 94/100, Best Practices 100/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 67/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

1

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

2

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

3

Reduce network delay

Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.

4

Make controls unambiguous

Give buttons and links accessible names, associate labels with fields, and use ordered headings and semantic regions. The same structure helps screen readers and software agents understand actions.

FCP1.2 s

First content

LCP1.2 s

Main content

CLS0

Layout stability

TBT60 ms

Blocking time

SI3.2 s

Visual speed

Metric glossary
FCP · First content
When the first text or image appeared on screen.
LCP · Main content
When the largest visible element in the first viewport rendered.
CLS · Layout stability
How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time
How long the browser main thread could not respond quickly to input.
SI · Visual speed
How quickly the visible viewport filled with content.
10/30/2026Lighthouse 13.6.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://snyfer.com/llms.txt
llms-full.txt

Full version is available

https://snyfer.com/llms-full.txt
ai.txt

ai.txt file was not found

robots.txt

File found

https://snyfer.com/robots.txt
Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Types: WebSite, Organization, SiteNavigationElement, SoftwareApplication, Dataset

OpenGraph90%

10 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotAllowed
OAI-SearchBotAllowed
ChatGPT-UserAllowed
Google-ExtendedAllowed
ClaudeBotAllowed
Claude-SearchBotAllowed
Claude-UserAllowed
BytespiderAllowed
CCBotAllowed
PerplexityBotAllowed
Perplexity-UserAllowed

Sitemaps

Declared discovery routes for crawlers and agents.

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 90%
og:image:typeimage/png
og:image:width1200
og:image:height630
og:site_nameSnyfer
og:typewebsite
og:urlhttps://snyfer.com/
og:localeen_US
og:titleSnyfer: Automated Website Forensics and Threat Intelligence
og:descriptionLook beyond a website with Snyfer. Run a free browser scan, inspect forensic evidence, explore connected domains and understand the findings behind its Trust Score.

Schema.org markup

Structured entities and properties exposed on the homepage.

Types found: 5 · Properties: 9
WebSiteOrganizationSiteNavigationElementSoftwareApplicationDataset
nameSnyfer
urlhttps://snyfer.com
descriptionFree forensic website scanner. Check any domain against antivirus engines, financial regulators and blacklists, and see the scam networks it is connected to.
potentialAction{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://snyfer.com/scan?domain={search_term_string
publisher{"@id":"https://snyfer.com/#organization"}
logohttps://snyfer.com/favicon.png
sameAshttps://x.com/snyfer_com, https://www.youtube.com/@Snyfer_com, https://www.facebook.com/profile.php?id=61593756253511, https://www.instagram.com/snyfer_com/, https://github.com/snyfer-official, https:
contactPointhttps://snyfer.com/contact
dateModified2026-10-29T06:45:05.141000000+00:00
# Snyfer

> Snyfer publishes website risk reports based on technical scans, shared infrastructure,
> regulatory warnings and moderated community reports.

A score is an assessment of recorded signals, not proof of fraud or a guarantee of safety.
Check each report's scan date, evidence and limitations. Current availability is separate
from the historical scan; an expired observation means unknown, not necessarily offline.
Shared technical traits do not by themselves prove common ownership. Claims made by an
analysed website must be attributed to that website.

Reports can be unpublished or withdrawn. Use the existing network and signal pages to
explore related domains. Each report links its Markdown, JSON, CSV and STIX exports. Consult
robots.txt and page-level directives for crawling and indexing rules.

## Reports and evidence

- [Wormwin report in Markdown](https://snyfer.com/api/export/md/wormwin.com): machine-readable findings for one published report.
- [Xesowin report in Markdown](https://snyfer.com/api/export/md/xesowin.com): another published report and its recorded findings.
- [Scan a website](https://snyfer.com/scan): look up a domain or request a scan.
- [Networks](https://snyfer.com/networks): domains connected by recorded technical signals.
- [Signals](https://snyfer.com/signals): technical fingerprints and their associated domains.
- [Infrastructure](https://snyfer.com/infrastructure): hosting and registration relationships.
- [Regulatory warnings](https://snyfer.com/warnings): notices attributed to their issuing authorities.
- [Community reports](https://snyfer.com/reports): moderated testimony, distinct from technical findings.

## Methodology

- [How scanning works](https://snyfer.com/docs/how-scanning-works): data collection and the scan process.
- [Trust Score](https://snyfer.com/trust-score): scoring signals and interpretation.
- [The graph](https://snyfer.com/docs/the-graph): correlation evidence and its limits.
- [Documentation](https://snyfer.com/docs): the complete guide directory.
- [API access](https://snyfer.com/developers): integration information and access requirements.

## Publisher and policies

- [About Snyfer](https://snyfer.com/about): the project and its editorial approach.
- [Dispute a report](https://snyfer.com/dispute): corrections and supporting evidence.
- [Contact](https://snyfer.com/contact): publisher enquiries and security disclosures.
- [Privacy policy](https://snyfer.com/privacy-policy): processing of personal information.
- [Cookie policy](https://snyfer.com/cookie-policy): browser storage and analytics.
- [Extension privacy](https://snyfer.com/extension-privacy): Snyfer Shield's current data practices.

## Optional

- [Full technical documentation](https://snyfer.com/llms-full.txt): additional technical reference.
- [Browser extension](https://snyfer.com/extension): Snyfer Shield.
- [Tools](https://snyfer.com/tools): available website and security tools.
- [Sitemap index](https://snyfer.com/sitemap_index.xml): indexable page inventory.
- [Robots policy](https://snyfer.com/robots.txt): crawler access rules.
Share or continue the analysis
Share this audit
Discuss with AI
Added 10/30/2026

Similar sites in the directory

Sites with a close AI-readiness score — compare how they set up llms.txt and markup.

snyfer.com - AI readiness audit | llmsmap.me