{"article":{"id":16335355751196,"url":"https://serankingteam.zendesk.com/api/v2/help_center/en-us/articles/16335355751196.json","html_url":"https://help.seranking.com/hc/en-us/articles/16335355751196-Verifying-SE-Ranking-Crawler-FAQ","author_id":16070358699292,"comments_disabled":false,"draft":false,"promoted":false,"position":6,"vote_sum":-4,"vote_count":30,"upvote_count":13,"downvote_count":17,"section_id":16332657216412,"created_at":"2024-10-11T05:52:44Z","updated_at":"2026-10-23T09:02:22Z","name":"Verifying SE Ranking Crawler FAQ","title":"Verifying SE Ranking Crawler FAQ","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-09-03T11:30:32Z","user_segment_id":null,"permission_group_id":15939478809756,"content_tag_ids":[],"label_names":[],"body":"
\n

SE Ranking Crawler is used to crawl websites for Website Audit and On-Page SEO Checker tools. By default, SE Ranking Crawler follows the instructions specified in the robots.txt file. However, this setting can be changed in the project configuration.

\n

The user agent of our crawler is SEBot-WA. You can verify if a web crawler using your server is truly SE Ranking Crawler by using one of the methods specified below.

\n

Reverse DNS method

\n

This is the preferred verification method. All servers used by SE Ranking Crawler have domain names that are subdomains of sr-srv.net (this domain is owned and exclusively used by SE Ranking).

\n

Step 1: Run a reverse DNS lookup on the IP address in question:

\n
\n$ host 144.76.237.123
123.237.76.144.in-addr.arpa domain name pointer cloud106.sr-srv.net\n
\n

Step 2: Verify that the resulting domain name is the subdomain of sr-srv.net.

\n

Step 3: Run a forward DNS lookup on the resulting domain name:

\n
\n$ host cloud106.sr-srv.net
cloud106.sr-srv.net has address 144.76.237.123\n
\n

Step 4: Confirm that the resulting IP address matches the original IP address.

\n

IP Match Method

\n

You can also verify SE Ranking Crawler by matching its IP with the official list of addresses below.

\n
\n

\n Current SE Ranking Crawler IP addresses\n

\n\n
\n
    \n
  • 5.9.48.208
    • \n
  • 23.88.36.149
    • \n
  • 37.27.13.192
    • \n
  • 37.27.22.37
    • \n
  • 37.27.22.127
    • \n
  • 37.27.29.8
    • \n
  • 46.4.81.149
    • \n
  • 62.238.32.219
    • \n
  • 116.202.175.208
    • \n
  • 136.243.103.47
    • \n
  • 138.201.137.152
    • \n
  • 142.132.195.214
    • \n
  • 144.76.14.242
    • \n
  • 144.76.15.151
    • \n
  • 144.76.69.81
    • \n
\n\n
    \n
  • 144.76.164.62
    • \n
  • 144.76.237.123
    • \n
  • 162.55.94.175
    • \n
  • 162.55.94.176
    • \n
  • 162.55.244.19
    • \n
  • 167.233.95.57
    • \n
  • 167.233.145.180
    • \n
  • 167.233.148.147
    • \n
  • 167.233.156.129
    • \n
  • 168.119.64.236
    • \n
  • 176.9.41.54
    • \n
  • 176.9.64.179
    • \n
  • 176.9.74.49
    • \n
  • 178.63.105.151
    • \n
\n
\n
\n

Still getting a 403 after whitelisting these IPs? The list above is a current snapshot, but SE Ranking Crawler’s addresses are assigned dynamically and can change over time — for Website Audit, some requests are also routed through a dedicated proxy pool — so a newer crawler IP may not yet appear in this list. For an allowlist that keeps working when the IPs change, allow the crawler by its user agent (SEBot-WA) or by the Reverse DNS method above (every crawler host resolves under *.sr-srv.net), instead of relying on a fixed IP list alone. Also check whether your firewall, CDN, or WAF has rules that override the IP allowlist — for example, region-specific blocking or bot-protection rules that reject the crawler even when its IPs are whitelisted. Note that a crawl can also be stopped by your site’s robots.txt rules or, on password-protected sites, by missing HTTP authentication in the audit settings — these are separate from an origin 403.

\n\n
","user_segment_ids":[]}}