vignanam.org is ranked in the top 10,000 sites and was registered in 2010. We couldn’t read its page: it turned our scanner away.

This site turns automated visitors away, as many large sites do, so we couldn’t read its page. What public records say is below; the score needs the page.

Among the top 10K sites.

A popularity band, not a visit count.

Tranco: #22,326 · Chrome UX Report: Top 10,000 · Majestic Million: Not ranked

Each list, with its date
SourceSaysAs of
TrancoA research ranking that combines several traffic and link sources, published daily.#22,326list of 27 Oct 2026
Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly.Top 10,000Sep 2026
Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0Not rankedlist of 28 Oct 2026
Was this answer right?

No framework or CMS shows in the page; it uses CDN, DNS, Email.

Everything else it uses (4)

Around it: CDN, DNS, Email.

Was this answer right?

We couldn’t read the page; outside records are below.

Signals, not a judgement: missing details are common on small, honest sites.

  • Domain registered25 Nov 2010, 15 years agoNoted
  • HTTPSLoads over HTTPS with a valid certificateFound
  • Security filterNot blocked by Cloudflare’s security filter and Quad9’s security filterNoted
Every signal we looked at

On the site

  • Contact pageBot protection hid the pageCouldn’t check
  • About pageBot protection hid the pageCouldn’t check
  • Privacy policyBot protection hid the pageCouldn’t check
  • TermsBot protection hid the pageCouldn’t check
  • Refund or returns policyBot protection hid the pageCouldn’t check
  • Contact detailsBot protection hid the pageCouldn’t check
  • Company detailsBot protection hid the pageCouldn’t check
  • Payment providersBot protection hid the pageCouldn’t check
  • TrackersBot protection hid the pageCouldn’t check

Behind the site

  • Security filterNot blocked by Cloudflare’s security filter and Quad9’s security filterNotedCloudflare’s security filter and Quad9’s security filter
  • Domain registered25 Nov 2010, 15 years agoNoteddomain registry
  • HTTPSLoads over HTTPS with a valid certificateFound
  • Protective settingsBot protection answered instead of the siteCouldn’t check
  • Email protectionPartly protected against forged emailPartlyDNS records

A second opinion on its security setup: Mozilla’s HTTP Observatory grades the site when you open it. Ten checks before you buy · A signal looks wrong? Report it

Was this answer right?

What it is

Website Summary

We couldn’t read the page, so we can’t say what it is.

We couldn’t read the page, so there are no words of its own to quote.

We couldn’t read the page, so we can’t say what kind of site it is.

More about it: Wikidata, profiles, AI use, page facts

AI use

  • AI training: asks GPTBot, ClaudeBot, anthropic-ai, CCBot and 1 more to stay away.
  • AI assistants: asks PerplexityBot to stay away.
Show evidence (6)Hide evidence
Exhibit 1 · robots.txt, line 1
User-agent: GPTBot · Disallow: /
Exhibit 2 · robots.txt, line 4
User-agent: ClaudeBot · Disallow: /
Exhibit 3 · robots.txt, line 7
User-agent: anthropic-ai · Disallow: /
Exhibit 4 · robots.txt, line 10
User-agent: CCBot · Disallow: /
Exhibit 5 · robots.txt, line 16
User-agent: Bytespider · Disallow: /
Exhibit 6 · robots.txt, line 13
User-agent: PerplexityBot · Disallow: /
Is this wrong? Report it

What its robots.txt and robots tags ask of AI crawlers. Each crawler chooses whether to follow it.

Site name
Not given
Language
Not given
What it tells search engines
None

Read from what the page says about itself; we haven’t checked whether it’s true.

Was this answer right?

Built with AI?

AI Website Detector

We couldn’t read the page, so we couldn’t look for traces.

AI traces: Couldn’t check

How we know

AI site builders leave traces in the sites they make. We look for the traces of 53 of them and show every match with the line it came from, so you can check it yourself.

We test this on 2,263 sites whose makers we know, and publish what we get wrong.

How we test it · Every builder we know · How to tell if a site was built with AI

Was this answer right?

It keeps 6 of 51 AI crawlers out, for training and for answers.

We couldn’t read its page: its bot protection turned our scanner away.

We couldn’t check enough of the site to score its AI readiness: the score needs its home page. Its badge comes with the score, so there is none to add yet.

What to fix

Optional: a fix few sites have yet
  • Files for AI agents

    Now None of the 8 we look for.

    If agents could use the site, publish what they need where they look.

    Details

    Why it matters: Agents act for people: they look for these files to know what a site lets them do. Worth it only if agents can use the site.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    If AI agents could use https://vignanam.org for its visitors (to search it, book, buy or sign in), publish what they need at the standard addresses, and only what the site really offers: an MCP server card at /.well-known/mcp/server-card.json if it runs an MCP server, an API catalog at /.well-known/api-catalog (RFC 9727) listing its public APIs, and OAuth protected resource metadata at /.well-known/oauth-protected-resource (RFC 9728) if agents sign in.

Left out of the score, as we couldn’t check them: Text without scripts, Search listing, Title and description, Structured data, llms.txt, Links for AI tools, Markdown copy.

Every check, with its evidence

Can AI find it?

  • robots.txtFound, 36 linesFound
  • SitemapListed in robots.txtFound
    Show evidenceHide evidence
    Exhibit 1 · robots.txt, line 53
    Sitemap: https://vignanam.org/sitemap.xml
    Is this wrong? Report it
  • Links for AI toolsThe site’s bot protection turned our scanner awayCouldn’t check
  • Search listingThe site’s bot protection turned our scanner awayCouldn’t check

Can AI read it?

  • Text without scriptsThe site’s bot protection turned our scanner awayCouldn’t check
  • Markdown copyThe site’s bot protection turned our scanner awayCouldn’t check
  • llms.txtThe site’s bot protection turned our scanner awayCouldn’t check
  • Title and descriptionThe site’s bot protection turned our scanner awayCouldn’t check
  • Structured dataThe site’s bot protection turned our scanner awayCouldn’t check

Can agents use it?

  • API catalogThe site’s bot protection turned our scanner awayCouldn’t check
  • Sign-in for AI agentsThe site’s bot protection turned our scanner awayCouldn’t check
  • Auth.mdThe site’s bot protection turned our scanner awayCouldn’t check
  • AI catalogThe site’s bot protection turned our scanner awayCouldn’t check
  • MCP serverThe site’s bot protection turned our scanner awayCouldn’t check
  • Agent cardThe site’s bot protection turned our scanner awayCouldn’t check
  • Agent SkillsThe site’s bot protection turned our scanner awayCouldn’t check
  • Agents in DNSNone foundNot found

What it lets AI do

Not scored

Keeping AI out is the site’s choice, so it never lowers the score.

  • AI trainingOpenAI and Common Crawl kept out, Anthropic and ByteDance partly; the rest let inPartly
  • AI answers and searchPerplexity partly; the rest let inPartly
Every AI crawler, and how we checked

AI companies

  • OpenAIChatGPTTo train its modelsKept outGPTBotline 1To answer people and searchLet inOAI-SearchBotChatGPT-User
  • AnthropicClaudeTo train its modelsPartlyClaudeBotline 4, kept outanthropic-ailine 7, kept outClaude-Weblet inTo answer people and searchLet inClaude-SearchBotClaude-User
  • GoogleGeminiTo train its modelsLet inGoogle-ExtendedTo answer people and searchLet inGoogle-CloudVertexBot
  • PerplexityTo train its modelsNone namedTo answer people and searchPartlyPerplexityBotline 13, kept outPerplexity-Userlet in
  • MetaMeta AITo train its modelsLet inmeta-externalagentFacebookBotTo answer people and searchLet inmeta-externalfetchermeta-webindexer
  • AppleApple IntelligenceTo train its modelsLet inApplebot-ExtendedTo answer people and searchNone named
  • AmazonTo train its modelsLet inAmazonbotTo answer people and searchLet inAmzn-SearchBotAmzn-User
  • Common Crawlopen data for trainingTo train its modelsKept outCCBotline 10To answer people and searchNone named
  • ByteDanceTo train its modelsPartlyBytespiderline 16, kept outTikTokSpiderlet inTo answer people and searchNone named
  • MistralLe ChatTo train its modelsNone namedTo answer people and searchLet inMistralAI-User

None of the 27 other AI crawlers we know is kept out.

What it tells AI crawlers

  • Content SignalsNoneNot found
  • A “noai” tagIts bot protection turned our scanner awayCouldn’t check

Like 30% of the 2,806 popular sites whose robots.txt we’ve read since 29 Oct 2026, it keeps at least one AI training crawler out. Of the 3,443 popular sites we’ve checked since 29 Oct 2026, 12% have a page drawn by scripts, 3% send a Markdown copy, 13% have an llms.txt and 5% offer a file for AI agents. How many websites block AI crawlers?

We read the site once, as our named bot: its robots.txt, read as crawlers read it, its home page and the files AI tools ask sites for. What we couldn’t read says so. robots.txt asks and doesn’t enforce: a firewall can treat AI crawlers differently from us.

Was this answer right?

Score breakdown

Site Score

No score: we couldn’t read the page, and outside records alone would mislead.

Why each part scored what it did
Was this answer right?

Domain history

Domain History

Registered in 2010; first archived in 2007.

  1. First captured by the web archiveInternet Archive
  2. Domain registeredRDAP
  3. This scanCheckAnySite

In the web archive: captured in 17 of 20 years · see the first capture

  1. 2007: captured
  2. 2008: no capture
  3. 2009: no capture
  4. 2010: no capture
  5. 2011: captured
  6. 2012: captured
  7. 2013: captured
  8. 2014: captured
  9. 2015: captured
  10. 2016: captured
  11. 2017: captured
  12. 2018: captured
  13. 2019: captured
  14. 2020: captured
  15. 2021: captured
  16. 2022: captured
  17. 2023: captured
  18. 2024: captured
  19. 2025: captured
  20. 2026: captured

No captures 2008–2010: the site may have been offline or parked then, or the archive didn’t visit.

The web archive saw this address on 13 Feb 2007, before its current registration on 25 Nov 2010. It was probably registered again, possibly by a new owner.

Changes, earlier scans and alerts
Since our previous scan
This is our first scan of the site.

Get an email when a new scan finds changes here (AI traces, technology, trust, title, score). Needs a free account.

Was this answer right?

How we scanned it

Only from what anyone can see: the site’s public pages and public records.

  • Politely. Our scanner, CheckAnySiteBot, says who it is and follows the site’s robots.txt.
  • With sources. Every fact above says where it came from and when.
  • Without guessing. When we couldn’t check something, we say so.
This scan, in numbers

933 checks on 4 Nov 2026, with version 0.6.0 of our checks and version 1.1 of the score.

How we work · What each version changed · About our scanner

Questions about vignanam.org

How old is vignanam.org?

Its domain was registered on 25 Nov 2010, 15 years ago. See the evidence

How popular is vignanam.org?

It is among the top 10,000 sites, by Tranco and Chrome UX Report. See the evidence

More sites near it in popularity

Automated findings from the site’s public home page and public records, as of 4 Nov 2026. They describe what we found, not the people or business behind the site, and they may be incomplete or out of date. This is information, not advice. Terms · Report an error

What this scan can’t tell you
  • Whether the business is real, honest or delivers what it sells.
  • Whether a site was made with AI when no traces were left: coding assistants and hand edits leave none.
  • How many people visit: we show popularity bands from public lists, not visits.
  • Anything beyond the home page as it was at the time of the scan.

Is this your site? Ask for a correction.