Kinsta

A site behind Cloudflare answers from Cloudflare’s addresses, so from the outside its real server is invisible. Kinsta knows it, and knows a good deal more about the sites it hosts. Connecting a Kinsta company lets CheckRoost read that, without anything installed on the sites.

What it does in CheckRoost

• Every site Kinsta hosts, with its environments, PHP version and WordPress version, on the Platforms page.
• The origin address behind a CDN. It fills in the address the blocklist check measures, so a Cloudflare site’s reputation is its own server’s and not Cloudflare’s.
• Plugin and theme versions with pending updates, for a site that has no CheckRoost plugin on it yet.
• Backup age, and a warning when the last backup is more than two days old — a failure nothing on the site itself can report.
• CDN bandwidth and visits this month.
• Sites nobody is monitoring. A hosted site with no monitor is listed, with a way to create one.

Hooking it up

1. 1

   Step 1. Create an API key in MyKinsta

   MyKinsta→Company settings→API keys.
2. 2

   Step 2. Find the company ID

   The idCompany value in the MyKinsta address bar, which is also on Company settings → Billing details. It is asked for with the key because every Kinsta request is scoped to a company: a valid key against the wrong company is refused, and checking them together is the only test that means it will work.
3. 3

   Step 3. Paste both into CheckRoost

   Settings→Integrations→Kinsta, as an owner or admin. The confirmation says how many sites Kinsta reports on that company.

How sites are matched to monitors

By domain, never by name — a site called “Maci’s Prime BBQ” is macisprimebbq.com, and the names share nothing. A site is linked to a monitor automatically only when its primary domain matches exactly one monitor; anything less certain waits on the Platforms page for you to confirm. The stakes set that line: a linked site supplies the address the blocklist check measures, so a wrong link would report somebody else’s server as your client’s reputation. A link you make, and a link you remove, is never undone by a later sync.

How often it reads

Sites, environments, addresses and versions every fifteen minutes. Plugins, backups and usage hourly, because they move daily or monthly and each costs Kinsta another request per site.

Where it and the plugin overlap

Kinsta and the CheckRoost plugin both report PHP and WordPress versions and plugin updates. Where a site runs both, the plugin’s reading is the one used, because it reads the running site rather than the host’s inventory — and an inventory scan can come back empty for reasons that have nothing to do with the site, such as a PHP version the scanner cannot run under. When that happens the page says the scan found nothing, never that the site has no plugins. What only the host can see — the origin address moving, a suspension, backups stopping — is reported either way.

Read-only

Kinsta’s API can restart PHP, clear caches, update plugins and restore backups. CheckRoost calls none of that: it reads.

Disconnecting

Removes the key and stops the sync. Delete the key in MyKinsta as well; removing CheckRoost’s copy does not cancel it.