SPF
Which services are authorized to send mail for your domain, and whether the record has obvious configuration problems.
Focused email authentication help
Know whether someone can impersonate your business email.
We check SPF, DKIM and DMARC, explain what the results actually mean, and help small businesses close email authentication gaps.
✓ Clear findings. Practical next steps. No changes without your approval.
Domain authentication REVIEWED
YOUR DOMAINyourbusiness.com
SPFSender
→DKIMSignature
→DMARCPolicy
THE GOALTrusted mail is easier to verify
A clearer signal for receiving mail systems, with fewer gaps for impersonators to exploit.
Evidence before claims
Plain English findings
Authorized changes only
Why it matters
Your customers trust the name in the From: line.
Invoices, contracts, payment instructions and sensitive documents arrive by email every day. When a domain’s authentication is incomplete or misconfigured, receiving mail systems may have less reliable guidance for separating legitimate messages from impersonation attempts.
DMARC works with SPF and DKIM to help verify who is allowed to send as your domain. It also tells receiving systems what to do when a message fails those checks.
EXAMPLE
Fromaccounts@yourbusiness.com
SubjectUpdated payment details
Hi James,
We’ve updated our bank details. Please use the new account shown on the attached invoice for payment due this Friday.
Account name Your Business Ltd
Sort code 20-XX-48
Account number XXXX 4821
Please confirm once the payment has been arranged.
Thanks,
Accounts team
Why this matters: a believable message can put money, data and customer trust at risk. We never send a test like this without explicit authorization.
What we check
The records behind trusted business email.
One focused review. Four layers of context. A result you can actually act on.
DKIM
Whether your email carries a verifiable signature and where alignment may need closer review.
DMARC
Your published policy, reporting setup and how receiving systems are instructed to handle authentication failures.
Posture
The combined picture, explained as practical risk rather than a page of DNS terminology.
What you receive
A useful answer, not a scanner dump.
- ✓ Authentication findings
- ✓ Risk explained in plain English
- ✓ Prioritized next steps
- ✓ Implementation guidance where agreed
- ✓ Re-check after approved changes
Our process
Careful by design.
The service begins with observation and explanation. Remediation is a separate, authorized step.
Observe
Review relevant DNS and email authentication records as they appear at the time of assessment.
Explain
Translate the configuration into a realistic risk assessment, including uncertainty and limitations.
Plan
Identify the safest order of work before any production record is changed.
Act with approval
Configuration support proceeds only under a separately agreed scope, with explicit authorization and change control.
Who it’s for
Small teams with a lot riding on email trust.
Especially organizations without a dedicated email security specialist.
Accounting & finance
Legal services
Recruitment & HR
Property businesses
Healthcare practices
B2B professional services
Safe scope
Assessment first. Production changes only by agreement.
A first look at a domain is observational. It is not a penetration test, does not involve sending impersonated mail, and does not authorize access to systems or changes to DNS.
Any implementation or remediation work requires written authorization, an agreed scope and information about legitimate sending services. Because mail systems and third party providers change, no assessment can guarantee prevention of every phishing, spoofing, delivery or security incident.
i Findings reflect the records and information available at the time of review. Business decisions and production changes remain subject to the client’s approval.
Start with your domain
Not sure whether your business email is properly protected?
Send the domain you use for email. We’ll review its authentication setup without asking for passwords or mailbox access.
What information is collected?
This version of the site uses no account signup, tracking cookies or analytics. If you email us, the domain, contact details and message you provide are used to respond to your request and manage the resulting conversation.
Does a domain check prove that email is secure?
No. It is a focused review of email authentication posture based on the records available at that time. It is not a comprehensive security audit, penetration test or guarantee against phishing, account takeover, delivery failures or other incidents.
Will you change our DNS during the first look?
No. A first look is observational. Production changes require explicit authorization and a separately agreed scope after legitimate sending services and operational risks have been understood.