Reputation Monitoring
Testing Domain Reputation with Spamhaus and Google Postmaster Tools
Authentication (SPF, DKIM, DMARC) proves who is allowed to send mail — but it says nothing about whether receivers actually trust your domain. Reputation monitoring closes that gap by showing how blocklists and major mailbox providers currently view your sending domain and IPs.
Why reputation checks matter
Even a fully authenticated domain can be throttled or sent to spam if its IP or domain reputation degrades due to high complaint rates, spam traps, or sudden volume spikes. Checking reputation regularly lets you catch problems before they damage deliverability across an entire campaign.
Blocklist statusIs your domain or sending IP listed on a known spam blocklist?
Inbox placementIs Gmail actually delivering to the inbox, or routing to spam?
Sender score trendIs reputation improving, stable, or declining over time?
Checking reputation with Spamhaus
What Spamhaus does
Spamhaus maintains widely-used real-time blocklists (DNSBLs) — including the SBL, XBL, PBL, and the Domain Block List (DBL) — that many mail servers consult before accepting incoming email. A listing on any of these can cause silent delivery failures or mass spam-folder routing.
Step-by-step domain and IP check
- Open the Spamhaus lookup tool. Go to the Spamhaus Intelligence / Block List Removal Center lookup page and enter your sending domain or the IP address of your mail server.
- Review each list separately. Check results across the DBL (domain-based), SBL (spam sources), XBL (exploited hosts), and PBL (policy block list for dynamic/residential IPs).
- Interpret a clean result. "Not listed" across all relevant lists means Spamhaus currently has no negative signal recorded for that identifier.
- Interpret a listing. If listed, Spamhaus shows the reason code and evidence category (e.g. spam trap hits, malware, compromised host) along with removal instructions.
- Submit a removal request if needed. Fix the underlying cause first (secure a compromised server, stop sending to purchased lists, etc.), then use the Spamhaus removal form and wait for re-evaluation.
- Re-check periodically. Run the same lookup weekly or after any large sending campaign, especially when warming up a new domain or IP.
Tip: check both the root domain and any dedicated sending subdomain (e.g. send.yourdomain.com) separately — a listing on one does not always affect the other.
Checking reputation with Google Postmaster Tools
What Google Postmaster Tools does
Google Postmaster Tools is a free dashboard that shows how Gmail specifically perceives your domain's sending reputation, spam rate, IP reputation, feedback loop, and authentication success rates — data you cannot get from blocklist lookups alone.
Step-by-step setup and monitoring
- Verify domain ownership. Sign in to Google Postmaster Tools and add your sending domain, verifying it via a DNS TXT record (similar to Search Console verification).
- Wait for data to populate. Postmaster Tools only shows data once you send a meaningful volume of mail to Gmail addresses — small volumes may show "not enough data."
- Check domain reputation. The Domain reputation chart buckets your domain into High, Medium, Low, or Bad — aim to stay at Medium or higher.
- Check IP reputation. Review the IP reputation graph for each sending IP; a sudden drop usually correlates with a spike in complaints or spam traps.
- Review spam rate. Gmail's own user-reported spam rate should stay well under 0.3 percent; rates above that threshold are strongly linked to inbox placement problems.
- Confirm authentication rates. The Authentication tab shows the percentage of your traffic passing SPF, DKIM, and DMARC — this should be close to 100 percent if your DNS records from Resend or Brevo are correctly published.
- Monitor feedback loop and encryption. Also check the delivery errors and encryption (TLS) tabs, since Gmail factors both into overall trust signals.
Using both tools together
| Signal | Spamhaus | Google Postmaster Tools |
| Scope | Global blocklist consulted by many mail servers | Gmail-specific reputation only |
| Best for | Detecting hard blocks and compromised infrastructure | Tracking spam-rate trends and inbox placement over time |
| Data requirement | Works immediately on any domain/IP | Requires real Gmail sending volume and DNS verification |
| Action on issue | Submit delisting request after fixing root cause | Reduce volume, clean list, improve engagement, re-warm domain |
Common pitfalls
- Checking only the root domain and missing a listing on the dedicated sending subdomain, or vice versa.
- Ignoring Postmaster Tools because "not enough data" appears — this simply means volume to Gmail is too low yet, not that reputation is fine.
- Ramping up sending volume too quickly on a freshly authenticated domain, which spikes spam complaints and tanks Google's domain reputation score.
- Not separating transactional and marketing streams — a spike in marketing complaints can drag down the reputation of transactional mail sharing the same domain.
Frequently asked questions
- How often should I check Spamhaus?
- Check weekly during normal sending, and immediately after any large campaign, domain migration, or unexpected deliverability drop.
- Does a clean Spamhaus result guarantee inbox delivery?
- No. Spamhaus only reflects blocklist status; Gmail, Outlook, and other providers apply their own separate reputation scoring, which is why Google Postmaster Tools is checked independently.
- Can a new domain show reputation data right away?
- Not usually. Postmaster Tools needs a verified domain and consistent Gmail-bound sending volume before meaningful data appears, which is one reason gradual domain warm-up matters.
- What should I do if my domain reputation drops to Low or Bad?
- Pause or reduce sending volume, remove unengaged or invalid addresses from your list, confirm SPF/DKIM/DMARC are still passing, and rebuild reputation gradually with smaller, well-targeted sends.
Contact ontiscal.com if you want to rent quality and aged domain names with an already clean reputation history, configured through custom DNS records for platforms like Resend or Brevo.