Check my connection

Verify a bot

Is the “Googlebot” or “GPTBot” in your logs real? Enter its IP address, its user agent, or both. We check the address against the lists the operators publish and against reverse DNS, because a user agent can say anything.

Result

Note: Claims to be Bingbot

Evidence

Evidence
User agent
bingbot
Claims to be
Bingbot · Microsoft · Search engine
Official lists
List (1)
robots.txt
Not stated in any documentation we could read

A user agent is text the client writes about itself, and anyone can copy Bingbot's. It is a claim, not proof. Add the IP address to verify it.

What to do: Add the IP address from the same log line to check the claim.
Check a whole log

Official lists

Official lists
Bingbot
Couldn't check: List · our copy Nov 15, 2026; dated Jan 3, 2024 by the operator

What this means and where the data comes from

Where the data comes from

  • Many bot checkers trust the user agent, or use address lists that are months old. We download each operator's own list every 6 hours and compare addresses with our copy. Operators also date their lists, and some dates are old: we show both, so you can judge.

The same check as plain text, for scripts:

curl "https://iplover.com/api/verify-bot.txt?ua=bingbot"

Checking a whole log? Paste it into the log checker: it reads the user agents in your browser and flags addresses that claim to be a crawler they are not. The log never leaves your device.

The lists we check against

Many bot checkers trust the user agent, or use address lists that are months old. We download each operator's own list every 6 hours and compare addresses with our copy. Operators also date their lists, and some dates are old: we show both, so you can judge.

ListProvesEntriesOur copyOperator's date
Google common crawlers (Googlebot)Googlebot317Nov 20, 2026Nov 20, 2026
Google special-case crawlers (e.g. AdsBot)Google special-case crawlers272Nov 20, 2026Nov 20, 2026
Google user-triggered fetchersGoogle user-triggered fetchers1612Nov 20, 2026Nov 20, 2026
BingbotBingbot29Nov 15, 2026Jan 3, 2024
ApplebotApplebot24Nov 15, 2026Sep 15, 2026
DuckDuckBotDuckDuckBot486Nov 15, 2026Sep 1, 2026
OpenAI OAI-SearchBotOAI-SearchBot39Nov 15, 2026Jan 2, 2026
PerplexityBotPerplexityBot21Nov 18, 2026Nov 18, 2026
Anthropic crawlers (ClaudeBot, Claude-User, Claude-SearchBot)Claude-SearchBot, ClaudeBot, Claude-User14Nov 15, 2026Oct 20, 2026
Amazon Amzn-SearchBotAmzn-SearchBot816Nov 15, 2026Sep 8, 2026
OpenAI GPTBotGPTBot18Nov 15, 2026Sep 22, 2026
Common Crawl CCBotCCBot5Nov 15, 2026Aug 11, 2026
AmazonbotAmazonbot1292Nov 15, 2026Sep 8, 2026
OpenAI ChatGPT-UserChatGPT-User237Nov 15, 2026Nov 6, 2026
Perplexity-UserPerplexity-User10Nov 15, 2026Oct 28, 2026
Amazon Amzn-UserAmzn-User1023Nov 15, 2026Nov 4, 2025
AhrefsBot and AhrefsSiteAuditAhrefsBot81Nov 15, 2026not dated

These bots publish no addresses, so they can only be recognised by their user agent, which proves nothing: meta-webindexer, meta-externalagent, Bytespider, Timpibot, FacebookBot, meta-externalfetcher, cohere-ai, SemrushBot, DotBot, MJ12bot, facebookexternalhit, Diffbot, omgili.

What this tool does

Bots announce themselves in the user agent, but that is just text: a scraper can call itself Googlebot or GPTBot in one line of code. What it can't fake is where the request comes from.

So this tool checks the address. Most large operators publish the IP ranges their crawlers use; we download those lists every 6 hours. Some also give their crawler addresses reverse-DNS names under their own domain; we look the name up and check that it points back to the same address.

Give a user agent and an address together for a verdict: verified, fake, a real bot using another bot's name, or not verifiable because the operator publishes nothing to check against.

How to read the results

  • Verified: the address is in the operator's own list, or its reverse-DNS name is under the operator's domain and points back to the address.
  • Fake: the user agent names a bot that publishes its addresses, and this address isn't one of them.
  • Can't be verified: the bot publishes no addresses, so the user agent is all there is. That is not evidence either way.
  • The lists table shows when we last downloaded each list and the date the operator gives it. An old operator date means the operator hasn't updated it, not that our copy is old.

Frequently asked questions

Why not just trust the user agent?

Because anyone can send any user agent. Scrapers often pretend to be Googlebot because many sites let it through. The address can't be faked for a completed web request.

What does “forward-confirmed” reverse DNS mean?

Whoever controls an address can give it any reverse-DNS name, even one ending in googlebot.com. Looking that name up again and getting the same address back proves the operator of the domain agrees, because only it controls that domain.

Why can't some bots be verified?

Their operators publish neither IP ranges nor reverse-DNS names. Then the user agent is the only sign, and it proves nothing. We say so instead of guessing.

Is my query stored?

No. The address is compared with our copy of the lists and looked up in DNS and the registries, like any IP check. We keep no record of what you check.

Can I check many addresses at once?

Yes: paste a server log into the log checker. It reads the user agents in your browser and flags addresses that claim to be a crawler they are not. Our sources are on the data sources page.