SPF · DKIM · DMARC · Lookalikes

Mail that fakesyour domaingets refused.

We set up SPF, DKIM and DMARC on your domains, move DMARC to reject without breaking the mail you send, and watch for lookalike domains registered to impersonate you.

How a spoof gets caught

Filtering powered byCyberSentriq

Inbound check
From
Accounts <accounts@yourcompany.in>
To
ap@yourclient.in
Subject
Updated bank details for invoice 4471
SPFfail203.0.113.47 not permitted
DKIMnonemessage not signed
DMARCfailnot aligned · p=reject
Lookalikenoneexact domain

domain policy says reject

Rejected
Gmail & Yahoo require DMARC since
Feb 2024
Outlook.com enforcing since
May 2025
CERT-In phishing report due within
6 hrs
DPDP penalty for weak safeguards, up to
₹250 Cr
How a spoof gets caught

Three DNS records. One decides.

Each protocol answers one question about an incoming message. None is enough on its own. Together, with DMARC at enforcement, they let receiving servers refuse mail that only pretends to be yours.

  1. 01

    SPF

    Is this server allowed to send for the domain?

    What it checks

    The receiving server compares the connecting IP address against the list of senders your domain publishes in DNS.

    What it misses alone

    It checks the hidden envelope sender, not the From address people read, and it breaks when mail is forwarded.

    yourcompany.inTXT
    v=spf1 include:_spf.google.com include:sendgrid.net -all
  2. 02

    DKIM

    Did the domain sign this message, and is it unchanged?

    What it checks

    Your mail servers sign each outgoing message. Receivers verify the signature against the public key you publish in DNS.

    What it misses alone

    A valid signature only proves which domain signed it. An attacker can sign mail perfectly well with a lookalike domain they own.

    s1._domainkey.yourcompany.inTXT
    v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAu3x…
  3. 03

    DMARC

    Does the visible From domain line up, and what happens if it doesn't?

    What it checks

    Requires SPF or DKIM to pass for the same domain shown in From, tells receivers to reject what fails, and sends you a report of who tried.

    What it misses alone

    It is only as strong as its policy. At p=none it reports spoofing and blocks none of it.

    _dmarc.yourcompany.inTXT
    v=DMARC1; p=reject; adkim=s; aspf=s; rua=mailto:dmarc@yourcompany.in
The engagement

Getting to p=reject without losing a single real email.

Many domains publish DMARC and stop at p=none, which reports spoofing and blocks none of it. The work is aligning every real sender so the policy can tighten safely.

  1. 01inventory

    Find every sender

    CRM, billing, HR, ticketing, newsletters: anything that sends as your domain. We build the list from DMARC reports, not from memory.

  2. 02p=none

    Watch without blocking

    DMARC goes live in report-only mode. Each legitimate sender gets SPF and DKIM aligned while nothing is being turned away.

  3. 03p=quarantine

    Send failures to spam

    Tighten in stages. A sender we missed lands in a spam folder, where it can be found and fixed, instead of vanishing.

  4. 04p=reject

    Refuse spoofed mail

    Receiving servers turn away mail that fails. Reports keep arriving, so a new tool that starts sending as you shows up in the next one.

Filtering layer

A real sender can still send a bad message.

SPF, DKIM and DMARC prove where mail came from, not whether it is safe to open. Filtering covers that at two points on the route. It runs on CyberSentriq's platform, and we set it up and tune it for your mail.

Powered byCyberSentriq
Runs both layersGateway · In-mailbox
01MX gateway
Before delivery

Stopped at the door

Your MX records point to the gateway, so every inbound message is checked for spam, malware and phishing before it reaches your mail server.

Connects via
MX records
Sees
all inbound mail
Runs on
CyberSentriq
02In-mailbox (ICES)
After delivery

Checked where it lands

Connects to your cloud mailbox by API and inspects mail after it arrives, where a gateway has no view, including mail between your own users.

Connects via
mailbox API
Sees
delivered and internal mail
Runs on
CyberSentriq
Beyond authentication

What still gets through a perfect DMARC record.

Lookalike watch

Domains one keystroke from yours

DMARC protects the domain you own. It cannot stop someone registering one that looks like it. We watch new registrations for swapped letters, added words and new TLDs, and flag the ones with live mail servers, because those can send mail today.

Registered domainMail
  • y0urcompany.inparked
  • yourcompany.coparked
  • yourcompany-billing.inMX live
  • yourcornpany.inMX live
Matching new registrations against yourcompany.in

Payment-change fraud

The costliest emails often pass every check, because they come from a real vendor account that has been taken over. We flag the pattern instead.

From
accounts@yourvendor.in
Reply-To
yourvendor.accts@gmail.com
Asks
new bank account, this run

Evidence for the rules you answer to

Summaries, not legal advice.

DPDP Act, 2023

Section 8(5)

Data fiduciaries must take reasonable security safeguards to prevent a personal data breach. Failing to do so can draw a penalty of up to ₹250 crore.

CERT-In Directions, 2022

Annexure I

Phishing and identity theft are reportable incidents, due within 6 hours of noticing them, with logs kept for 180 days.

Gmail, Yahoo, Outlook.com

Bulk-sender rules

Domains sending 5,000+ messages a day must pass SPF and DKIM and publish DMARC, or risk having their mail rejected.

Before the first call

Questions we hear first.

Will moving to p=reject stop our own email?

Not if the senders are found first. That is what the p=none and quarantine stages are for: every legitimate service is aligned before anything is rejected, and the DMARC reports show anything that was missed.

We use Google Workspace or Microsoft 365. Isn't this already covered?

Their filters protect your inbox. They do not stop someone else sending mail that claims to come from your domain to your customers and vendors. Only your own SPF, DKIM and DMARC records do that, and those are yours to publish.

Whose platform does the filtering run on?

CyberSentriq's. Both the gateway and the in-mailbox layer run on it. We deploy it on your domains, switch your MX records over, tune the policies to your mail, and stay your point of contact for it.

Does this help our mail reach the inbox?

Usually. Gmail, Yahoo and Outlook.com now require authentication from bulk senders, and aligned mail is easier for receivers to trust. It will not fix content or list-hygiene problems on its own.

What do you need from us?

Someone who can change DNS for your domains, the list of tools you know send email, and an owner for each. The reports surface the ones nobody listed.

Domain review

Find out how far you are from p=reject.

Bring a domain. We read its public records with you and lay out what it takes to reach enforcement.

All services

What we look at

  • Your SPF record, and how close it is to the 10-lookup limit
  • Which DKIM selectors you publish, and their key lengths
  • Your DMARC policy, and whether anyone reads the reports
  • Lookalike domains that are already registered