Veribix

AI referrer domains

The hostnames AI assistants send traffic from, and — the column that actually matters — whether each one tells your analytics where the visit came from.

Use these hosts to build a channel group in Google Analytics, or to filter your server logs. Escape the dots if you are writing a regular expression, and order the AI channel above Referral, because GA4 stops at the first match.

Dataset version 2026-08-06, updated 2026-08-06. 11 records.

AI referrer domains, version 2026-08-06
Referrer hostAssistantStrips referrerAddedNotes
chatgpt.comChatGPTNo2026-08-06Also appends utm_source=chatgpt.com on outbound links, which survives referrer stripping.
chat.openai.comChatGPTNo2026-08-06Legacy host, still seen in historical analytics exports.
perplexity.aiPerplexityNo2026-08-06
gemini.google.comGeminiNo2026-08-06
bard.google.comGeminiNo2026-08-06Pre-rename host; appears in historical exports.
claude.aiClaudeYes — arrives as direct2026-08-06Outbound links are sent with rel="noreferrer", so most real visits appear as Direct.
copilot.microsoft.comMicrosoft CopilotNo2026-08-06
bing.comMicrosoft CopilotNo2026-08-06Copilot answers served inside Bing refer as bing.com; indistinguishable from ordinary Bing search without a UTM tag. Rows from this host are reported as estimated.
grok.comGrokNo2026-08-06
chat.deepseek.comDeepSeekNo2026-08-06
meta.aiMeta AIYes — arrives as direct2026-08-06

What the strips-referrer column means

2 of the 11 hosts here send outbound links with the referring page removed. When that happens the visit is real and the reader is real, and your analytics files it as direct traffic because nothing identifying the source was ever transmitted.

This is not a configuration problem and no tool recovers it afterwards. It means any AI referral figure — ours included — is a floor rather than a total, and it means the assistants most protective of their users are the ones your reports will show as sending nobody. See referrer stripping for what can still be measured.

Changelog