bigo.sg
Domduck has read bigo.sg on 7 days across 5 sources, since 2 August 2026. The domain was registered in 2014. Its robots.txt blocks none of the 8 AI crawlers Domduck tracks.
Last checked .
blocked
What changed
7 days of readings- 29 September 2026 (2026-09-29)
- Nameservers changed between 15 September 2026 and 29 September 2026, from ns3.dnsv5.com, ns4.dnsv5.com to ns-1347.awsdns-40.org, ns-1676.awsdns-17.co.uk, ns-473.awsdns-59.com, ns-631.awsdns-14.net.
- 15 September 2026 (2026-09-15)
- Nameservers changed between 31 August 2026 and 15 September 2026, from ns-1347.awsdns-40.org, ns-1676.awsdns-17.co.uk, ns-473.awsdns-59.com, ns-631.awsdns-14.net to ns3.dnsv5.com, ns4.dnsv5.com.
Popularity rank
73 days, lower is betterPosition in the Tranco list, a research ranking of the million most popular domains averaged over thirty days so a single day’s traffic spike cannot move it.
AI crawler policy
No robots.txt served · No llms.txtNo ChatGPT browsing or training
No ChatGPT search surface
No Claude retrieval
No Perplexity citation
Out of Gemini and AI Overviews grounding, Search ranking unaffected
Out of Apple Intelligence training
Out of most open training corpora
Out of TikTok and Doubao
Read from bigo.sg/robots.txt. “Not named” means the file says nothing about that agent, which is not the same as allowing it: a catch-all rule added later blocks it without anyone deciding to.
What the domain itself says
read directly, not from a vendor- Issuer
- GlobalSign nv-sa
- Valid
- Yes
- Expires
- 2027-01-03
- Protocol
- TLSv1.2
- Names covered
- 2
- A records
- 2
- AAAA records
- 0
- Mail exchangers
- 1
- Nameservers
- ns-1347.awsdns-40.org, ns-1676.awsdns-17.co.uk, ns-473.awsdns-59.com, ns-631.awsdns-14.net
- DMARC policy
- quarantine
- Registered
- 2014-08-08
- Registrar
- Key-Systems GmbH
- Registry status
- active
Questions
- Does bigo.sg block GPTBot?
- No. bigo.sg's robots.txt does not disallow GPTBot, though it does not name the agent either.
- Does bigo.sg publish an llms.txt file?
- No. Domduck found no llms.txt at bigo.sg.
- When was bigo.sg registered?
- 8 August 2014, through Key-Systems GmbH.
- Who issues bigo.sg's certificate?
- GlobalSign nv-sa.
How this page is made
Every number on this page is a measurement Domduck took itself or read from a public source, on a stated date. Nothing here is written by a language model. Where a value has not changed, no sentence is generated about it.
First reading . 5 sources, 7 days with at least one reading. The popularity rank comes from the Tranco list; the registration record from RDAP, which ICANN requires registries to publish. The certificate, the DNS records and the crawler policy are read by Domduck directly from bigo.sg.