google.co.id
No scorethe page couldn’t be read
google.co.id is ranked in the top 10,000 sites and was registered in 2004. 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: #2,143 · Chrome UX Report: Top 10,000 · Majestic Million: #3,114
Each list, with its date
| Source | Says | As of |
|---|---|---|
| TrancoA research ranking that combines several traffic and link sources, published daily. | #2,143 | list of 7 Oct 2026 |
| Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly. | Top 10,000 | Aug 2026 |
| Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0 | #3,114 | list of 8 Oct 2026 |
Technology
Tech Stack CheckerNo framework or CMS shows in the page; it uses CDN, Email.
Everything else it uses (2)
Around it: CDN, Email.
CloudflareCDNShow evidenceHide evidence
Evidence · response headerPopular sites using Cloudflare Is this wrong? Report itcf-ray: a49a003c3ae000cf-KIX
Google WorkspaceEmailShow evidenceHide evidence
Evidence · DNS recordPopular sites using Google Workspace Is this wrong? Report itgoogle.co.id MX 0 smtp.google.com.
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 registered18 Dec 2004, 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 registered18 Dec 2004, 21 years agoNoteddomain registry
- HTTPSLoads over HTTPS with a valid certificateFound
- Protective settingsBot protection answered instead of the siteCouldn’t check
- Email protectionProtected against forged emailFoundDNS 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
AI use
- AI training: doesn’t ask AI training crawlers to stay away.
- AI assistants: may read it for the people who ask them.
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.
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,312 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
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 2004; first archived in 2005.
- Domain registeredRDAP
- First captured by the web archiveInternet Archive
- This scanCheckAnySite
In the web archive: captured in 22 of 22 years · see the first capture
- 2005: captured
- 2006: captured
- 2007: captured
- 2008: captured
- 2009: captured
- 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: captured
- 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
924 checks on 12 Oct 2026, with version 0.5.0 of our checks and version 1.1 of the score.
More sites near it in popularity
Automated findings from the site’s public home page and public records, as of 12 Oct 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.