W webatla
Log in Get started

About webatlabot

webatlabot is the web crawler operated by webatla. It visits public web pages and records which technologies a site runs on. If you arrived here from a User-Agent string in your logs, everything you need to identify, verify or block the crawler is on this page.

Last updated 2026-08-24

1How to identify the crawler

User-Agent
Mozilla/5.0 (compatible; webatlabot/1.0; +https://webatla.com/bot; abuse@webatla.com)
Request header
From: abuse@webatla.com
IPv4 address
46.224.210.134 → crawl.webatla.com
IPv6 address
2a01:4f8:1c19:79a5::1 → crawl.webatla.com
Abuse contact
abuse@webatla.com

Every request the crawler makes carries that exact User-Agent string and that From header. Traffic comes from the two addresses above and from no others.

2What the crawler does and does not do

  • ✓Requests public pages over HTTP and HTTPS, the same way a browser does.
  • ✓Reads the returned HTML and the response headers to work out what software the site runs.
  • ✓Follows ordinary redirects and records the final URL.
  • ✗Does not submit forms, log in, or attempt authentication of any kind.
  • ✗Does not scan ports and does not probe for vulnerabilities.
  • ✗Does not execute JavaScript and does not collect personal data from pages.

3How to check that a request really came from us

Both of our addresses have reverse DNS pointing at crawl.webatla.com, and that hostname resolves back to the same two addresses. Check both directions before you trust a request.

# reverse lookup on the IPv4 address
dig -x 46.224.210.134 +short
crawl.webatla.com.

# forward lookup has to return the same address
dig +short crawl.webatla.com
46.224.210.134

# the same check for IPv6
dig -x 2a01:4f8:1c19:79a5::1 +short
crawl.webatla.com.

A User-Agent string on its own proves nothing. Anyone can send our User-Agent. If a request claims to be webatlabot but the address fails the check above, it is not us, and we would like to hear about it.

Note that crawl.webatla.com is the crawler host only. This page and the rest of the site are served from different addresses behind a CDN, so a lookup of webatla.com will not match.

4Why the crawler reached an address you do not recognise

The crawler works from public domain listings and from DNS. If a domain still points at your IP address, the crawler connects to that address, even when the domain has nothing to do with you any more.

That is the usual explanation for an unexpected visit. A former customer moved away and left an A or AAAA record aimed at your range, or a parked domain resolves to a host you have since taken over.

Send us the domain name along with the address and we can confirm what happened. Correcting the stale DNS record at the source stops every crawler, not only ours.

5How to stop the crawler

Blocking works straight away and needs nothing from us. Match on the User-Agent token webatlabot, or on the two addresses.

# block by User-Agent (Apache)
SetEnvIfNoCase User-Agent "webatlabot" bad_bot
Deny from env=bad_bot

# block by address (Linux firewall)
iptables -A INPUT -s 46.224.210.134 -j DROP
ip6tables -A INPUT -s 2a01:4f8:1c19:79a5::1 -j DROP

You can also write to the address below and ask us to exclude your domains or your address range. We action exclusion requests within one business day and confirm by email once the change is live.

6Contact

A person reads this address: abuse@webatla.com

  • •The domain name or IP address involved
  • •A few log lines, with timestamps and the time zone
  • •What you would like us to do (block a domain, exclude a range, or explain a particular request)
  • •An address we can reply to