Set Up Google Postmaster Tools for Your Domain in cPanel
Gmail's Postmaster Tools shows your spam rate and authentication. Add one TXT record in cPanel Zone Editor, verify the domain, and see Gmail's own dashboards for free.
The short answer
Add the sending domain in Google Postmaster Tools, copy its verification TXT or CNAME value, and save that record at the DNS provider your nameservers actually use. Record the provider-side DNS rows before editing; a dig result is evidence, not a restorable zone backup. Verification is typically immediate but can take up to 10 minutes, while dashboard data usually updates within 24 hours and may remain empty at low Gmail volume.

Reading options
On this page
- What Google Postmaster Tools actually is
- Before you start
- Find out where your DNS lives
- Record the current DNS state before you add anything
- Set up Postmaster Tools step by step
- A worked example of the finished zone
- When your DNS is outside cPanel, such as Cloudflare
- How to check it worked
- Troubleshooting
- Pro tips and security notes
- The one message worth forwarding
- Reader questions
- Sources & further reading
Before you start
You need a Google account, control of the real authoritative DNS provider, a provider export or written inventory of current DNS rows, and the exact verification value Google supplies. Do not replace existing SPF, DKIM, DMARC or MX records.
To set up Google Postmaster Tools for a domain hosted in cPanel, you add the domain in Postmaster Tools, copy the TXT record Google gives you, and save that record in cPanel > Domains > Zone Editor. Once Google finds the record, the domain shows as verified and the dashboards start filling with data about mail you send to Gmail users.
Two things Gmail pays close attention to are how often people mark your mail as spam and whether it passes authentication. Postmaster Tools is the free dashboard that shows you both, and the cPanel part takes about ten minutes.
By the end of this guide you will have a verified domain in Postmaster Tools, a way to confirm the record from your own terminal, and a short list of numbers worth watching every week.
What Google Postmaster Tools actually is
Postmaster Tools is a set of dashboards from Google that report how Gmail sees the mail coming from your domain. It shows your spam rate, your domain and IP reputation, how much of your mail passes SPF, DKIM and DMARC, how much arrives over an encrypted connection, and which delivery errors Gmail returned.
Think of it as the report card a school sends home. You cannot see inside the classroom, but the card tells you how the teacher rates you, and it tells you early enough to change something before the final grade.
One limit to know up front: the data only covers messages sent to personal Gmail accounts, meaning addresses ending in @gmail.com or @googlemail.com. Mail you send to a company that uses Google Workspace does not appear here.
Why this matters: Google's sender guidelines encourage senders to check their email compliance status using Postmaster Tools. If you never look, the first sign of trouble is usually a customer saying your invoice went to their spam folder.
Before you start
- Login access to cPanel for the hosting account that holds the domain.
- A Google account. A free Gmail account works, and so does a Google Workspace account.
- Access to wherever the domain's DNS is really managed. That is cPanel only if your domain uses the hosting server's nameservers.
- About ten minutes of hands-on time, plus a short wait for DNS to update.
- A note of your current SPF, DKIM and DMARC status, so you know where you stand before the dashboards tell you.
For the last item, cPanel has a page that checks this for you. Google's guidelines name SPF, DKIM, DMARC and a PTR record (reverse DNS, which maps your sending IP address back to a hostname) as requirements, so it helps to know which of those you already have.
If any of SPF, DKIM or DMARC is missing, set them up first or right after this guide. Our walkthrough on setting up SPF, DKIM and DMARC for small business email covers each record.
Find out where your DNS lives
Skip this and you can waste an hour. The Zone Editor only matters if the internet actually asks your cPanel server about your domain.
Run this command in a terminal (Terminal on macOS, or any Linux shell) to see which nameservers answer for your domain.
dig +short NS example.comYou will see one hostname per line. If the names belong to your hosting provider, your DNS lives in cPanel and you can follow the Zone Editor steps. If they belong to Cloudflare or to your domain registrar, the record has to go there instead, and you can skip to the section for DNS providers outside cPanel.
Quick tip: if you are unsure which hosting account a domain points to, our guide on mapping a host to a domain explains how nameservers and records fit together.
Record the current DNS state before you add anything
You are adding one TXT record. First export the zone from your DNS provider if it offers an export, or record the existing TXT rows with their Name, TTL, Type and Record values. That provider-side inventory is the useful rollback record.
You can also save a public DNS snapshot from a terminal:
dig +noall +answer TXT example.com > example-com-txt-public-before.txtOpen the file and you should see the TXT records currently published at the root domain, often including a line with v=spf1. This dig output is evidence, not a restorable zone backup: it does not capture every DNS name or the provider's unpublished settings. Keep both the provider export or inventory and the public snapshot until verification is complete.
Heads up: cPanel's documentation warns that resetting a zone file erases your record changes. Never use a reset option in the Zone Editor as a way to "clean up" before this task, and do not edit or delete an existing SPF, DKIM or DMARC record while adding Google's separate verification value.
Set up Postmaster Tools step by step
At the time of writing (17 November 2026), Google's setup article sends you to the current interface at https://postmaster.google.com/v2/manage_domains, and links to a notice about the deprecation of the old Postmaster Tools interface. If the screens look different from what follows, the official steps are in Google's Postmaster Tools setup article.
Step 1: Add the domain in Postmaster Tools
Sign in with your Google account and open the Manage Domains page. Click Add new domain at the top right, type your domain, and click Create.
Google asks you to add the domain you use for SPF, DKIM or both. In practice that means the domain in the DKIM signature (the d= value) or the domain in the Return-Path address. For most small businesses sending from their own mailbox on cPanel, that is simply the main domain, for example example.com.
What you should see: the domain appears in your Manage Domains list. Click Back at the top left if you need to return to the list.
Step 2: Copy the verification record
On the Manage Domains page, click More options to the right of the domain name, then click Verify domain. A window titled "Verify ownership of domain" opens with a TXT or CNAME record.
Copy the TXT value exactly as shown. Google's TXT verification article gives this format as an example, and your own value will have a different string after the equals sign.
google-site-verification=abcdef123_456wx789yzLeave this window open. You will come back to click Verify.
Quick tip: there is a Not now button that lets you finish setup without verifying. Avoid it. Google is clear that no email data appears until the domain is verified.
Step 3: Open the Zone Editor in cPanel
Log in to cPanel and go to cPanel > Domains > Zone Editor. You will see a list of the domains on the account.
Find your domain and click Manage. A new screen opens with a table of records, using the columns Name, TTL, Type, Record and Actions.
What you should see: your existing records, including your MX records and at least one TXT record if SPF is already set up. You can type into the filter box or pick a record type filter to narrow the list to TXT.
Step 4: Add the TXT record
Click Add Record, or click the arrow next to it and choose TXT from the menu. A form row appears.
Fill it in like this:
- In the Name box, enter the domain itself with a trailing dot, for example example.com followed by a dot. cPanel's documentation uses the same notation for subdomains, such as prefix.example.com followed by a dot.
- Leave the TTL as it is unless you have a reason to change it.
- Make sure the Type is TXT.
- In the Record box, paste the full verification value, including the part before the equals sign.
Now stop and read the Record box once more before saving. cPanel's own documentation says the Record text box "will accept invalid data", so it will not warn you about a stray space, a missing character or an extra pair of quotation marks you copied by accident.
Click Save Record. If you have more than one pending row, Save All Records saves them together.
What you should see: the new record appears at the top of the table, with Type TXT and your verification value in the Record column.
Heads up: do not edit or replace your existing SPF record to make room for this one. A domain can publish the verification TXT record and the SPF TXT record side by side. They do different jobs.
Step 5: Click Verify in Postmaster Tools
Go back to the "Verify ownership of domain" window and click Verify. Google says verification is typically immediate, though the status can take up to 10 minutes to update.
What you should see: the domain's status changes to verified on the Manage Domains page. If it fails, do not panic, and do not add a second record yet. Go to the checks in the next section first.
Step 6: Share access with your team (optional)
If a developer, a colleague or your host needs to see the dashboards, you can add them. On Manage Domains, click More options next to the domain, click Manage users, click New user at the top right, enter the person's Google email address and click Add.
Only verified domains can be shared, and the other person needs a Google or Google Workspace account. Postmaster Tools does not notify them, so send them a message yourself.
A worked example of the finished zone
Made-up example — do not paste these values into live DNS: a small online bakery uses example.com for its shop and sends order confirmations and a monthly newsletter from orders@example.com. Its example mail server is 192.0.2.10, an address reserved for documentation. After this guide, the illustrative TXT records look like this in standard zone-file notation.
example.com. 3600 IN TXT "v=spf1 ip4:192.0.2.10 ~all"
example.com. 3600 IN TXT "google-site-verification=abcdef123_456wx789yz"
_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=none"The first line is an illustrative SPF record, the second is a fake Postmaster Tools verification token, and the third is an illustrative DMARC record. Replace all example values with records supplied by your real mail and DNS providers. The TTL values are illustrative too, so keep whatever your zone already uses.
Notice that the verification record does not touch the other two. If your zone ends up with two records beginning v=spf1, stop and compare the zone against your provider export or recorded inventory; a domain should publish one SPF record that combines its authorized senders.
How to undo only this change
In the same DNS provider where you added it, delete only the TXT or CNAME row containing the exact Google verification token from Step 2. Leave existing SPF, DKIM, DMARC, MX and unrelated TXT records unchanged. Save, then run the dig check below until that exact token no longer appears. Removing the token can affect future ownership checks, so keep it unless you are intentionally removing the domain from Postmaster Tools.
When your DNS is outside cPanel, such as Cloudflare
If the nameserver check showed Cloudflare, add the record in the Cloudflare dashboard instead. Records you add in the cPanel Zone Editor will not be seen by anyone in this case, because the internet asks Cloudflare, not your hosting server.
Cloudflare's documentation for creating DNS records gives these steps:
- In the Cloudflare dashboard, open the DNS Records page for your domain.
- Select Add record.
- Choose TXT as the Type.
- For the name, use @ to mean the root of the domain, as Cloudflare's zone apex page describes. Google's TXT article also says to leave the host blank or enter @.
- Paste the full verification value into the record's value field.
- Select Save.
Cloudflare notes one exception: if a hosting partner added your domain to Cloudflare, you manage DNS records through that partner, not the Cloudflare dashboard.
Other DNS providers and registrars work the same way: add a TXT record with @ or a blank host, paste the value, save, then click Verify in Postmaster Tools.
How to check it worked
There are two places to confirm the result: public DNS and Postmaster Tools itself.
Run this from a terminal to ask DNS for your domain's TXT records in short form.
dig +short TXT example.comYou should see your verification value among the lines, wrapped in quotation marks, next to your SPF record.
"v=spf1 ip4:192.0.2.10 ~all"
"google-site-verification=abcdef123_456wx789yz"If the record is missing, ask one of your domain's own nameservers directly, which rules out a stale cache on your network. Replace the server name with one of the names the NS check returned.
dig @ns1.example.com +short TXT example.comThen check Postmaster Tools. On the Manage Domains page, the domain should show as verified. Give it a day before expecting charts: Google says dashboard data is typically updated within 24 hours, but can take longer, and the times are shown in UTC.
When data arrives, these are the numbers to watch:
- Spam rate: the share of your DKIM-authenticated mail that Gmail users reported as spam.
- Authentication: the percent of your mail that passes SPF, DKIM and DMARC.
- Compliance status: whether you meet Google's sender requirements, shown as Compliant, Needs work or No data found.
- Delivery errors: rejections and temporary failures, with the reasons Gmail gave.
At the time of writing (17 November 2026), Google's guidelines say senders should keep their spam rate below 0.1% and should never let it reach 0.3% or higher. You can pick date ranges of the last 7, 30, 60, 90 or 120 days, which makes it easy to see whether a bad week was a one-off.
Troubleshooting
"Your domain couldn't be verified"
Symptom: you click Verify and Postmaster Tools reports that it could not find the record. Likely cause: the record has not reached public DNS yet, or the value has a typo. Fix: wait a few minutes, run the dig check above, and compare the value character by character. Google's own advice is to wait, check the verification string, and try again with a new string if it still fails. Its general TXT article adds that changes can take up to 72 hours to be recognized across the internet.
The record is in Zone Editor but dig cannot see it
Symptom: the TXT record sits in the Zone Editor table, yet dig +short TXT example.com shows only your old records, even when you ask a nameserver directly. Likely cause: your domain's nameservers point somewhere else, so the cPanel zone is not the one the world reads. Fix: run dig +short NS example.com and add the record at the provider those nameservers belong to.
The value has extra quotes or spaces
Symptom: dig shows the record, but with doubled quotation marks, a leading space or a broken string, and Google still refuses it. Likely cause: the value was pasted with surrounding quotes or extra whitespace, and the Zone Editor accepted it because the Record box accepts invalid data. Fix: click Edit next to the record, paste the clean value, and click Save Record.
Verified, but the dashboards are empty
Symptom: the domain is verified, but charts are blank or show "No data found". Likely causes: it has been less than a day, your daily volume to personal Gmail addresses is low, or you added a domain that is not the one in your DKIM or SPF. Google says dashboards might not include all data on low-volume days, to protect user privacy. Fix: wait at least 24 hours, send your normal mail, and confirm that the domain you added matches the d= domain in your DKIM signature.
A colleague sees "not authorized"
Symptom: someone opens a dashboard link you shared and gets a "not authorized" message. Likely cause: they were never added as a user, or they signed in with a different Google account. Fix: add their exact Google address under More options > Manage users > New user, then tell them which account to sign in with.
Compliance status does not change after you fix something
Symptom: you corrected DMARC or DKIM, but the Compliance status dashboard still says Needs work. Likely cause: Google says it can take up to 7 days for changes to show. Also, this dashboard covers primary domains only, not subdomains. Fix: wait a week, and check the primary domain's entry.
Pro tips and security notes
Add the primary domain first. Google says that once the primary domain is verified, its subdomains do not need separate verification, though you still add them to the list if you want their data. Keep in mind that the Domain Reputation dashboard only shows messages sent from the exact domain used for DKIM and SPF authentication.
Each Google account that needs its own access, as opposed to shared access, needs its own verification record. If your agency and your in-house developer both verify separately, you will end up with two google-site-verification TXT records, which is fine.
Leave the verification record in place. Google's TXT article warns that removing a verification record before Google confirms ownership makes verification fail, and keeping it costs you nothing.
Check that the PTR record exists for your sending IP, because Google's guidelines require one. In cPanel, the Email Deliverability page at cPanel > Email > Email Deliverability shows the status of each domain's DKIM, SPF, DMARC and reverse DNS records. Its Repair option is unavailable when the server does not control the domain's DNS, which is another clue that your DNS lives elsewhere.
Guard your DKIM private key. cPanel's documentation warns that exposing it is a security risk, because someone else could sign mail and pass as you. Nobody setting up Postmaster Tools ever needs the private key, only the public record in DNS.
Quick tip: if you are planning a hosting move soon, our guide on lowering DNS TTL before a hosting move explains why TXT records like this one should come along to the new zone untouched.
If you send newsletters, know where the bigger rules start. At the time of writing (17 November 2026), Google defines a bulk sender as one that sends close to 5,000 messages or more to personal Gmail accounts within 24 hours, and bulk senders must have SPF, DKIM and a DMARC record with at least p=none. One-click unsubscribe is required only for marketing and promotional messages.
Once DMARC is running, the reports it produces show who is sending as your domain. Our guide to reading DMARC aggregate reports pairs well with the Authentication dashboard.
Ask your host or a developer for help when:
- The domain verifies but the Authentication dashboard shows a low DKIM pass rate.
- Your sending IP has no PTR record, since only the owner of the IP address can usually set one.
- Delivery errors show rejections you do not understand.
- You use a third-party sender such as a newsletter platform and are unsure which domain signs the mail.
The one message worth forwarding
If someone else manages your DNS, send them this and fill in your domain and value.
Hi,
Please add one TXT record to the DNS for example.com so I can verify the domain in Google Postmaster Tools.
Host or Name: @ (the root of example.com)
Type: TXT
Value: google-site-verification=abcdef123_456wx789yz
Please do not change or remove the existing SPF, DKIM or DMARC records. Add this as a separate record.
While you are in there, could you also confirm that our sending IP address has a PTR record, and that SPF, DKIM and DMARC are all published for example.com? Google lists all of these as sender requirements.
Once it is saved, I will click Verify on my side. Thanks.The takeaway: one TXT record in the right DNS zone gives you Gmail's own view of your sending reputation, and checking it weekly is the cheapest early warning your email will ever get.
Reader questions
Is Google Postmaster Tools free?
Yes. You only need a Google account and the ability to add a DNS record for your domain.
Does Postmaster Tools show mail sent to Google Workspace addresses?
No. Google says the data covers only messages sent to personal Gmail accounts, meaning addresses ending in gmail.com or googlemail.com.
Do I need to verify each subdomain separately?
No. Google says subdomains need no separate verification once the primary domain is verified, though you still add them to see their data.
What spam rate should I aim for?
Google's sender guidelines say to keep the spam rate below 0.1% and never let it reach 0.3% or higher.
Can two people verify the same domain?
Yes. Each Google account that verifies on its own needs its own verification record, or a verified owner can share access through Manage users.
Why does my Compliance status still say Needs work after a fix?
Google says changes can take up to 7 days to show on the Compliance status dashboard, and that dashboard covers primary domains only.
Was this guide helpful?
Help us make the next update better.
Sources & further reading
What changed
Verified Postmaster setup, verification timing, dashboard scope and cPanel TXT-entry behavior against current primary documentation. Reframed dig output as evidence instead of a zone backup, labeled all DNS examples as fictional documentation values, added a record-specific rollback and original accessible media.
Originally published . About our editorial updates.



