Free check · no account

Anyone can send email
pretending to be you.

Unless your domain is set up to stop them. Most aren’t — and the owners have no idea. Find out where yours stands in about thirty seconds.

Free, no account needed. We only read public DNS records — nothing is sent to your domain.

Reads public DNS and your TLS certificate. Nothing to install, no account, and we never touch your mail.

What comes back

Most tools tell you what’s wrong. We tell you what it lets someone do.

“SPF record missing’’ means nothing to the person who signs the cheque. “Anyone on the internet can send email that looks like it came from your finance director’’ gets fixed by Friday.

C
58 / 100
SPF doesn’t authorise Microsoft 365
Your DKIM records show you send through Microsoft, but SPF doesn’t list it — and your record ends in -all. Legitimate mail is being rejected. Usually the aftermath of a migration nobody finished.
DMARC is monitor-only
Reports are collected but nothing is blocked. Anyone can still send as you today.
Certificate valid for 74 days
2048-bit, issued by Let’s Encrypt. We’ll warn you 30 days before it lapses.
Why it matters

Email authentication stopped being optional

Your mail stops arriving

Google and Yahoo have required DMARC from bulk senders since 2024, and Microsoft has followed. Get it wrong and mail doesn’t bounce — it lands in junk, or vanishes. The invoices you assume arrived, didn’t.

Anyone can be you

Without DMARC at enforcement, sending mail that appears to come from your domain takes minutes and no special access. That’s the mechanism behind invoice fraud. The damage isn’t only financial — it’s your name on the email.

Your insurer is asking

Email authentication now sits on cyber insurance proposals alongside MFA and backups — baseline controls, not extras. Business email compromise is among the most common claim types.

The part nobody shows you

Every provider already knows who’s sending as you

Google, Microsoft and Yahoo publish a daily report naming every server that sent email using your domain. It’s free, it already exists, and almost nobody collects it.

Microsoft 365 40.107.22.14 · Dublin Your own mail, authenticating correctly. 100% 11,840
Mailchimp 198.2.180.66 · Atlanta Someone in marketing set this up. It half works. 61% 2,104
Unknown host 185.220.101.44 · Frankfurt Not yours. Sending as your company, to your customers. 0% 312

That last one is why this matters. The mail never touches your servers, so it appears in no log you own. The first you hear of it is a customer asking about an invoice you didn’t send.

DNS Watcher

“When did that change, and who changed it?”

Every email security tool tells you what your DNS says today. We keep a dated record of what it said every time we looked — and tell you the moment anything moves. No other DMARC platform does this.

acme.ie · change history
TXT record added: stripe-verification 2 March · a service was connected to your domain
DKIM record changed: selector1 18 February · 2048-bit key rotated
SPF record changed 4 January · marked as expected by you
And when something matters
MX record changed
14 March, 14:02
was acme-com.mail.protection.outlook.com
now mail.unknown-host.ru

Mail for this domain is now being delivered somewhere else. If this was a planned migration, no action is needed. If it wasn’t, your incoming email is being routed to a server you didn’t choose — treat it as urgent.

Changes that don’t look like problems

A swapped sending service. A rotated signing key. A new verification record for a tool nobody mentioned. None of these move a health score, so nothing else flags them — and they’re exactly what an attacker changes.

A record that outlasts the person

The contractor who set it up has moved on. The IT manager before this one left no notes. “It hasn’t changed since March” is an answer, and we can give it.

Evidence when it matters

After an incident, the first question is when it started. A dated before-and-after of every record turns a week of guesswork into a timestamp.

Already required of you

ISO/IEC 27001:2022
A.8.32
Change management. Changes to security-relevant configuration must be controlled and evidenced. DNS records governing email authentication are security-relevant configuration, and most organisations cannot produce a single record of who changed them or when.
ISO/IEC 27001:2022
A.8.15
Logging. Records of activity relevant to security must be produced and retained. A registrar’s own logs typically retain 90 days, are not exportable, and vanish entirely if you move registrar.
NIS2
Article 21(2)(e)
Security in maintenance. A configuration that was correct at deployment and silently degraded is precisely the failure this measure exists to prevent.
NIS2
Article 21(2)(b)
Incident handling. The first question after any incident is when it started. A dated before-and-after answers it in seconds instead of days.

We publish a full control-by-control mapping, including the measures we don’t cover — see it here.

DNS Watcher covers SPF, DMARC, MX, DKIM, nameservers and every other record on your domain — and the addresses behind them, not only the names. A mail server that keeps its hostname while the machine answering for it changes is the quietest way mail gets redirected, and comparing names alone would never see it. We call that drift, and we tell you what it means rather than only that it happened. Changes you made on purpose can be marked as expected — they stay in the record either way.

Arriving whether you're ready or not

Certificate renewals are about to get thirteen times more frequent

The CA/Browser Forum voted unanimously in 2025 to collapse how long a TLS certificate can last. The first cut has already happened.

Until March 2026 398 days Renew once a year. What most people still assume.
Since March 2026 200 days Twice a year. Annual renewal calendars are already wrong.
From March 2027 100 days Roughly quarterly. Manual processes start breaking here.
From March 2029 47 days Roughly monthly. Manual renewal is no longer realistic.

Why it matters more than it sounds

An expired certificate isn’t a warning — it’s a full-page browser block. Visitors leave. Payment flows fail. APIs refuse to connect.

And the ones that catch people out are never the certificate they’re watching. They’re the forgotten subdomain, the staging site that became production, the certificate someone set up before they left.

What we do about it

We check your certificates daily and warn you with a renewal window scaled to each certificate’s own lifetime — so the alert stays useful as the industry moves from 200 days to 47.

We also flag certificates short enough that renewing by hand has become a risk, and tell you what automating it would take. Most hosts already support it — people just don’t know.

The part you’ll be glad of later

When someone asks you to prove it

A cyber insurance renewal. A client security questionnaire. A board that read something worrying. All three end with the same question, and it isn’t a technical one.

What they ask

“What are you doing about email impersonation?”

Screenshots of a dashboard aren’t an answer. Neither is a technical export nobody in the room can read. What’s wanted is a dated document saying which domains are protected, what’s outstanding, and how it’s kept that way.

What you send

One page, your logo at the top, generated the moment you need it.

Every domain and its protection status in plain terms. What’s monitored and why it matters. Anything still open, with the date it was first found — because a document that only shows good news convinces nobody.

No spreadsheet to assemble, no screenshots to annotate, nothing to write up the night before.

Frameworks

You are already required to do most of this.

Nobody buys domain monitoring because a standard says so. But when the questionnaire arrives, or the auditor asks, or the insurer wants evidence, these are the clauses that turn out to have been about your email domain all along.

Where domain health lands

NIS2
Article 21(2)(d)
Supply chain security. A lookalike domain invoicing your customers is a supply-chain attack in which your brand is the weapon. Detecting registrations and evidencing that you monitor for them is the measure.
NIS2
Article 21(2)(h)
Cryptography. Certificate inventory with key strength, signature algorithm and expiry — including DKIM keys short enough that major providers will not trust them.
ISO/IEC 27001:2022
A.8.24
Use of cryptography. The same inventory, and the record that it is reviewed continuously rather than annually.
ISO/IEC 27001:2022
A.5.7
Threat intelligence. Lookalike detection and blocklist monitoring are threat intelligence about your own brand, collected rather than subscribed to.
Cyber insurance Proposal forms. Underwriters now ask whether DMARC is enforced and whether domain changes are monitored. Attaching evidence is a different conversation from ticking a box, and it is one held before a claim rather than during one.

We publish the full mapping, control by control, including the four NIS2 measures we don’t touch at all — read it here. A vendor page with no such section is worth asking about.

Why us

Most people fix this once, then find out later it broke

Email authentication isn’t a project you finish. It’s DNS, and DNS gets edited — by whoever set up the new CRM, the new invoicing system, the new marketing tool.

A consultant

Quotes a day rate, gets it right, sends an invoice.

They won’t be there in March when someone adds a sending platform and quietly breaks your SPF record. You’ll find out when a customer says they never got your quote.

A dashboard tool

Shows you raw DMARC data and leaves you to it.

Fine if you already know what an alignment failure means. If you don’t, you’re paying monthly for a screen nobody opens — and the problem stays unfixed.

Alerts you’ll still read in six months

The hard part isn’t noticing. It’s knowing when to say something.

Any tool can email you every time a number moves. Do that for a month and people stop reading — including on the day it matters.

We check before we alarm

A DNS lookup that fails momentarily makes a healthy domain look like it collapsed. Before sending anything that says your score fell off a cliff, we look again. If the second check disagrees, you hear nothing — because nothing happened.

We know what normal looks like

DMARC reports arrive in batches on each provider’s own schedule, so a day or two of quiet means nothing. We wait until the gap is genuinely unusual before mentioning it, rather than flagging a working domain every morning.

One email, not eleven

Routine findings across all your domains bundle into a single update, at the hour you choose. Set quiet hours and nothing arrives outside them.

The measure of a monitoring service isn’t how much it tells you. It’s whether you still open the email.

What they can see

Someone is already looking at your domain

Not metaphorically. Every certificate ever issued for your name is published in a public log that anybody can search, and it takes about four seconds.

The hosts you forgot about

staging. from a project that shipped in 2023. old-crm. from a migration nobody finished. vpn. from before the office moved. Each one still holds a live certificate, each one is listed publicly, and each one is a way in that isn’t on anybody’s asset register.

We read the same logs and hand you the list — then check what each host is actually serving: certificate expiry, key strength, TLS version.

The names that look like yours

A domain one character away from yours costs a few euro and is registered weeks before the first email goes out. That gap is the whole opportunity, and it is the only point at which this is cheap to deal with.

We generate the variants an attacker would actually use — the ones that survive being read quickly — and tell you which are registered, which are serving a site, and which are set up to send mail as you.

None of this data is ours, and none of it is secret. Certificate transparency logs, registration records and browser blocklists are all public, and the people planning to impersonate you read them as a matter of routine. There is no version of this where they cannot see your domain. The only question is whether you are looking at the same list they are — and whether you find out today or in six weeks, from a customer.

The difference

Three things you won’t get elsewhere

Written for the person who signs things

Every report opens with what the problem means for your business, not which DNS record is wrong. A director can read it in ten seconds and know whether to act. The technical detail is still there, further down, for whoever fixes it.

Proof, not screenshots

One dated document showing every domain’s status, what’s outstanding and how it’s maintained — with your logo on it. For the insurance renewal, the client questionnaire, the board pack. Generated the moment you need it, not assembled the night before.

Certificates, as the rules change

Certificate lifetimes are being cut industry-wide — 200 days now, 47 by 2029. Our warnings scale to each certificate’s own lifetime, so they stay useful as that shifts. Most monitoring still uses a fixed 30-day window, which will fire for two thirds of a certificate’s life by then.

People who answer

PhishAware is built and run by Symeon, an Irish IT and security company. You’re not filing a ticket into a queue in another timezone — and if you’d rather we just did the work, we can.

A fair question

“Nothing has gone wrong. Why are we still paying?”

Because something is being stopped, every day, and you don’t see it.

Once your domain is set to reject, mail pretending to be you is refused at the receiving server. Those attempts don’t reach anyone, so they never become a story — but they do show up in your reports. A quiet month is the product working, not the product being unnecessary.

Your reports show what was blocked, what changed, and how your score has moved since you started. That’s the evidence a quiet month is actually quiet.

DNS keeps changing

Every new tool that sends email touches your records. The break is never noticed by whoever caused it.

Lookalikes keep appearing

Domains resembling yours get registered continuously. Catching one at registration is far cheaper than after it sends.

Certificates keep shortening

Renewals move from yearly to roughly monthly by 2029. Manual tracking stops being realistic.

Before you sign with anyone

Four limits that only bite once you’ve moved in

None of these appear on a competitor’s pricing page. All four are standard.

The message cap

Your reports stop mid-month

Most tiers cap how many messages get analysed. Run one big campaign, or get hit by a spoofing burst — exactly when you need the data most — and you hit the ceiling. The reporting goes quiet and the upgrade prompt appears.

We don’t count messages. There is no ceiling to hit.

The history window

Your evidence expires

One to twelve months, depending on tier. So when an insurer asks what you were doing about email authentication last year, or you want to prove a spoofing campaign started in March, it’s gone — unless you were on the tier that keeps it.

We keep everything, on every plan, for as long as you’re with us.

The seat count

Someone ends up sharing a login

One to three portal users on lower tiers. So your IT provider, your compliance lead and whoever actually edits DNS can’t all have access — and the workaround everyone reaches for is sharing a password.

Unlimited users. Give access to whoever needs it.

The second invoice

Half of it is a different product

Lookalike domain detection, blocklist monitoring, certificate watching — usually separate products, separately priced, often from a separate vendor. Which is how a €35 tool becomes a €90 one.

All included. One price, one login, one invoice.

And the part they never mention: a report you can act on. Everyone shows you charts. We tell you which server is sending as you, where it is, whether it’s yours, and what to do — in language you can forward to whoever manages your DNS.

Two things we don’t do

Forensic reports. They contain copies of individual emails, sent to a third party — us. Under GDPR that makes us a processor of your correspondence. The major providers stopped sending them years ago for the same reason, so the tier that charges for them delivers a trickle. We’d rather not hold your customers’ email to sell you an upgrade.

SSO, API and domain discovery. Not yet. Ask if you need them and we’ll tell you honestly where they are.

Pricing

One product. Everything in it.

No modules to piece together, and no feature you discover you needed later. Priced per domain, with any part switchable off.

Free check

Find out where this domain stands, right now

€0

No account, unlimited, always free

  • 28 checks across SPF, DKIM, DMARC, MTA-STS and TLS
  • Plain-English explanation of every finding
  • The exact records to publish, ready to copy
  • Certificate expiry and blocklist status
  • A snapshot — nobody tells you when it changes
Check a domain

About ten seconds

Managed

For when you’d rather someone else did the work

€149 per month

Up to 5 domains included

  • Everything in Domain health, across up to 5 domains
  • We write the records; you paste them in
  • Guided move to enforcement without breaking real mail
  • We read the reports and tell you what needs doing
  • Named contact who knows your setup
  • Irish company, same timezone, answers the phone
Talk to us

Usually a 20-minute call to start

What’s covered Free check Domain health Managed
Configuration
SPF, DKIM, DMARC, MX and BIMI checksYesYesYes
Checked on a schedule, not just once–YesYes
The records written for you––Yes
Who’s sending as you
DMARC reports collected–YesYes
Sending sources named, not just IPs–YesYes
Guided move to enforcement––Yes
What the outside world sees
Lookalike domain detection–YesYes
Blocklist monitoringSnapshotMonitoredMonitored
Certificate expiry warningsSnapshotMonitoredMonitored
Key strength and signature algorithmYesYesYes
Issuer and self-signed detectionYesYesYes
Warnings scaled to certificate lifetime–YesYes
Apex and www both checked–YesYes
DNS Watcher
SPF, DMARC, MX and DKIM watched–YesYes
Nameserver changes detected–YesYes
New verification records spotted–YesYes
Before-and-after on every change–YesYes
Checked as often as hourly–YesYes
Immediate alert on a critical change–YesYes
Snapshot history you can look back through–YesYes
Mark a change as expected–YesYes
Proving it
Evidence pack for insurers and auditors–YesYes
Score history over time–YesYes

Monthly, cancel any time, no setup fee. For comparison: a consultant quotes a day rate to do this once, and won’t be there when a DNS edit six months later quietly breaks it.

Found problems? We’ll fix them.

Email authentication is fiddly and easy to get subtly wrong. Tell us what the check found and we’ll tell you exactly what it takes — usually within a day.