Verify site ownership
Prove your workspace controls a site's host with a meta tag or a DNS record: what a verification covers, the daily re-check and what makes it lapse.
Last reviewed
On this page
Verifying a site proves that your workspace controls the host the site lives on. You add a token to your site, either as a meta tag or as a DNS record, and OctoPing checks for it. This page covers what a verification covers, the two methods, who can do what, how the daily check keeps it current and what makes it lapse.
What a verification covers
- A verification belongs to one workspace and one host. The host is the name in the site's address, such as
example.com, without the path or the port. - It covers every site in the workspace on that host, so
example.comandexample.com/checkoutshare one. - The bare domain and the www host are separate hosts. Verify
example.comandwww.example.comeach. - Two workspaces can each verify the same host. An agency and its client can both prove control.
- You can only verify a host that one of the workspace's sites uses.
OctoPing never assumes ownership because a site responds, because the workspace added the site first or because a status page uses the domain. Only the token counts.
Verify a host
Open the site and start
On the site's page, find the Verify ownership section and choose Start verification. It shows a token and both methods with copy buttons.
Add the tag or the record
Add one of the two methods below. One is enough.
Verify now
Choose Verify now to check straight away, or wait for the daily check. The section shows what each method found.
The two methods
Meta tag
Add this tag to the head of the host's home page, with your own token:
<meta name="octoping-site-verification" content="YOUR-TOKEN">- OctoPing reads exactly
https://example.com/for your host, with the default port and no path. A tag on any other page, or on another port, does not count. - A site that is only reachable over http can't use the meta tag, so verify it with the DNS record. A host that is an IP address can't be verified at all.
- The tag has to be in the head of the page. A tag in the body or inside an embedded frame does not count.
- The order of the attributes, capital letters and extra spaces don't matter.
- OctoPing follows redirects when it reads the home page.
The home-page rule exists because a redirect or a page another person controls on a shared host could otherwise put a tag where the owner never meant it.
DNS TXT record
Create a TXT record at your DNS provider, with your own host and token:
| Type | Name | Value |
|---|---|---|
| TXT | _octoping-site.example.com | octoping-site=YOUR-TOKEN |
- The record name starts with
_octoping-site, then a dot, then the host. - Other TXT records on the same name are fine. OctoPing looks for the one that matches.
- This is a different record from the one custom status page domains use, which starts with
_octoping. Keep both if you use both.
Who can do what
| Role | What they can do |
|---|---|
| Viewer | See the status. A Viewer doesn't see the token, so they can't add it to a site. |
| Member, Admin and Owner | Start a verification, choose Verify now and reset it. |
Verify now checks the host once and shows the result. A second Verify now for the same host within 10 seconds is refused with a message, so repeated clicks don't repeat the work. A workspace whose trial ended or whose plan is paused can't use it.
Reset issues a new token and removes the verification. A tag or record with the old token stops matching.
How the daily check works
OctoPing re-checks every host with a started verification once a day, using both methods. Either one matching the token keeps the host verified.
- The page method uses the reading of the home page that OctoPing already made that day for a site of yours, or reads the home page itself.
- A host is only checked while the workspace has a monitored site on it.
A confirmation stays current for 14 days. A verified host that hasn't been confirmed in that long shows as not confirmed and counts as unverified until a check finds the token again, so a host that stopped being checked can't stay verified forever.
When a verification lapses
A day counts as a miss only when both methods give a definite answer: OctoPing read the home page and found no matching tag, and the DNS lookup answered that there is no matching record.
- Timeouts, DNS server errors and a home page that couldn't be read never count as a miss and never change the status.
- A home page isn't read while the site is down or in a maintenance window, so those days don't count either.
- A miss counts once per day.
The status becomes Lapsed when the daily check has found neither the tag nor the record on 7 days with no successful check in between. Days the check could not run neither count nor reset the count. The section shows how far into the count you are, such as "3 of 7 days without the tag or record", before that happens.
When a verification lapses, OctoPing emails the workspace's Owner and Admins once. The email says the tag and record were missing for 7 days and how to fix it. Putting the tag or the record back restores the verification at the next check, or straight away with Verify now, and a later lapse sends a new email.
Statuses
| Status | Meaning |
|---|---|
| Not started | Nobody has started verification for this host. |
| Waiting for the tag or record | Started, and OctoPing hasn't found the token yet. |
| Verified | The token was found and confirmed recently enough to count. |
| Lapsed | Both methods found nothing on 7 days with no successful check in between. |
What it is used for
Nothing yet. Verification only records that your workspace controls a host. No OctoPing feature changes what it does based on it today, and the page won't say otherwise until one does.
Related pages
- Checks reference covers the checks that run on a site.
- Custom domains covers the separate DNS record for a status page domain.
- Workspaces and team covers the roles.
Related
- DocsChecks referenceWhat each of the eight checks and heartbeats measures, whether it is on by default, how often it runs and what counts as a failure or a change.
- DocsCustom domainsServe a status page on your client's own domain: the plan requirement, the DNS records, the statuses a domain moves through and what the domain serves.
- DocsWorkspaces and teamHow a workspace is organized, what each role can do, how invitations and seats work, and how to group and change many sites at once.