CorbaCount

You spotted a CorbaCount request.

If CorbaCount turned up in your server logs, this page explains exactly what it is, why it visited, and how to recognise it. Short version: someone runs CorbaCount web analytics on a site, and we made a small, well-behaved automated request on their behalf.

The user-agent in your access log
Mozilla/5.0 (compatible; CorbacountScreenshotBot/1.0; +https://www.corbacount.com/bot)
  • Loads one page: the homepage
  • Twice a month, plus once when the site is added
  • Always links back to this page

Why did CorbaCount request my site?

CorbaCount is a privacy-friendly analytics tool. When a customer adds a website to their account, we make a few automated requests to that domain so their dashboard has a preview image and up-to-date domain-health data. These requests are infrequent, identify themselves honestly, and never crawl or index your pages.

Screenshot bot

Shows up in your access log

A headless Chromium browser loads the site's homepage to capture a thumbnail for the customer's dashboard.

  • One page, loaded like a normal browser would (with its images, CSS and scripts)
  • When the site is added, then on the 1st and 15th of each month
  • Identifies itself as CorbacountScreenshotBot

Certificate check

Does not show up in your access log

Powers the domain health panel: we read the site's public SSL certificate to warn the customer before it expires.

  • Once a week, on Monday
  • Only a TLS handshake on port 443 - no page is requested
  • Registration data comes from public registries, not from your server

When it visits.

A few requests a month per site. No bursts, no crawling, no repeated hammering.

  1. A customer adds the site

    The screenshot bot loads the homepage once, usually within a minute or two.

  2. Every Monday

    The certificate check reads the SSL certificate with a TLS handshake.

  3. 1st and 15th of the month

    The screenshot bot refreshes the thumbnail with one more homepage load.

  4. The site is removed

    All requests stop. Nothing is kept polling in the background.

How to recognise it.

Every HTTP request we make to your site carries this user-agent, pointing back to this page. If you see a different user-agent claiming to be CorbaCount, it is not us.

Data lookups

Requests to public registries and data providers, never to your website

CorbaCount/1.0 (+https://www.corbacount.com/bot)

What the CorbaCount bot will never do.

No crawling or indexing

It does not spider your links, scrape your content or build a search index. The screenshot bot loads a single page.

No load on your server

About two homepage loads a month, plus a weekly TLS handshake. Nothing a server would notice.

No visitor data collected

These requests are about the site itself. Visitor analytics only ever come from the tracking snippet a customer installs.

No disguising who we are

We never spoof a real browser to hide the request. The user-agent always says CorbaCount and links straight back here.

I do not use CorbaCount - why is it hitting my site?

Almost always it means someone with access to the site - an agency, a developer, a colleague - added it to a CorbaCount account to measure its traffic. If that is unexpected, check with whoever manages the site.

If you would like us to stop, or you believe the site was added without authorisation, tell us through the contact page and we will remove it.

Can I block it?

Yes. The screenshot bot sends a stable, identifiable user-agent, so you can return a 403 for anything matching corbacount. Blocking it simply means the customer's dashboard shows a placeholder image instead of a preview of your site.

# nginx, inside the server block
if ($http_user_agent ~* "corbacount") {
    return 403;
}

# Apache (.htaccess)
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} corbacount [NC]
RewriteRule .* - [F,L]

Still not sure what you are looking at?

Send us the log line - the user-agent, the IP and the timestamp - and a real human will tell you exactly what it was, within one business day.

Contact us