uiic.in
No scorethe page couldn’t be read
uiic
uiic.in is ranked in the top 10,000 sites and was registered in 2005. 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.
Popularity
Website Traffic CheckerAmong the top 10K sites.
A popularity band, not a visit count.
Top 1KTop 10KTop 100KTop 1MOutside top 1M
Tranco: #23,523 · Chrome UX Report: Top 10,000 · Majestic Million: Not ranked
Each list, with its date
| Source | Says | As of |
|---|---|---|
| TrancoA research ranking that combines several traffic and link sources, published daily. | #23,523 | list of 27 Oct 2026 |
| Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly. | Top 10,000 | Sep 2026 |
| Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0 | Not ranked | list of 28 Oct 2026 |
Technology
Tech Stack CheckerNo framework or CMS shows in the page; it uses CDN, DNS, Business tools.
Everything else it uses (3)
Around it: CDN, DNS, Business tools.
CloudflareCDNShow evidenceHide evidence
Evidence · response headerPopular sites using Cloudflare Is this wrong? Report itcf-ray: a5638dfcad194a5f-EWR
GoDaddy DNSDNSShow evidenceHide evidence
Evidence · DNS recordPopular sites using GoDaddy DNS Is this wrong? Report ituiic.in NS pdns13.domaincontrol.com.
GlobalSign (certificates)Business toolsShow evidenceHide evidence
Evidence · DNS recordPopular sites using GlobalSign (certificates) Is this wrong? Report ituiic.in TXT globalsign-domain-verification=97087E42D983834C06B7CC441443AD1B
Business tools can stay listed after a site stops using them.
Trust signals
Website Trust CheckerWe couldn’t read the page; outside records are below.
Signals, not a judgement: missing details are common on small, honest sites.
- Domain registered16 Feb 2005, 21 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 registered16 Feb 2005, 21 years agoNoteddomain registry
- HTTPSLoads over HTTPS with a valid certificateFound
- Protective settingsBot protection answered instead of the siteCouldn’t check
- Email protectionNot protected against forged emailNot foundDNS 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
What it is
Website SummaryWe 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
- 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.
Built with AI?
AI Website DetectorWe 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,275 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
AI access
AI Crawler CheckerIt lets every AI crawler in.
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.
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://uiic.in 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, Sitemap, llms.txt, Links for AI tools, Markdown copy.
Every check, with its evidence
Can AI find it?
- robots.txtNone, so every crawler may read every pageNot found
- SitemapThe site’s bot protection turned our scanner awayCouldn’t check
- 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 scoredKeeping AI out is the site’s choice, so it never lowers the score.
- AI trainingOpenAI, Anthropic, Google, Meta and 4 moreLet in
- AI answers and searchOpenAI, Anthropic, Google, Perplexity and 3 moreLet in
Every AI crawler, and how we checked
AI companies
It has no robots.txt, so the 24 crawlers of the 10 AI companies we know may read every page.
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
If this is your site
- Decide what AI may do with the site, and say it in robots.txt. Write the lines
Like 75% of the 1,305 popular sites whose robots.txt we’ve read since 29 Oct 2026, it keeps no AI training crawler out. Of the 1,611 popular sites we’ve checked since 29 Oct 2026, 11% have a page drawn by scripts, 3% send a Markdown copy, 10% have an llms.txt and 4% 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.
Score breakdown
Site ScoreNo score: we couldn’t read the page, and outside records alone would mislead.
Why each part scored what it did
Domain history
Domain HistoryRegistered in 2005; first archived in 2010.
- Domain registeredRDAP
- First captured by the web archiveInternet Archive
- This scanCheckAnySite
In the web archive: captured in 16 of 17 years · see the first capture
- 2010: captured
- 2011: captured
- 2012: captured
- 2013: captured
- 2014: captured
- 2015: captured
- 2016: captured
- 2017: captured
- 2018: captured
- 2019: captured
- 2020: captured
- 2021: captured
- 2022: captured
- 2023: captured
- 2024: no capture
- 2025: captured
- 2026: captured
Changes, earlier scans and alerts
- Since our previous scan
- This is our first scan of the site.
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 6 Nov 2026, with version 0.6.0 of our checks and version 1.1 of the score.
Questions about uiic.in
How old is uiic.in?
Its domain was registered on 16 Feb 2005, 21 years ago. See the evidence
How popular is uiic.in?
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 6 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.