omen.ru is a free email provider
omen.ru is a consumer mailbox provider, so anyone can open an address there in a minute.
59 /100
Good
Email authentication report card
What omen.ru publishes in DNS to stop other people sending mail in its name, read record by record.
Can mail be forged as this domain?
Yes, a forgery is delivered
no DMARC record is published, so a receiver that honours what this domain publishes is not told to reject a message with it in the From header, and delivers it.
- Weak
SPF ~all
The record ends in ~all. Mail from a host outside the list is only marked, not rejected, so it usually still arrives.
- Fail
DMARC No record
No DMARC record is published, so receivers get no instruction and judge a forged message on SPF and DKIM alone.
- Weak
MTA-STS Not published
No MTA-STS policy, so a sending server has nothing that tells it to insist on verified TLS for this domain.
- Weak
DNSSEC Not signed
The zone is not signed. A resolver has no cryptographic way to tell a real answer from a forged one.
- Weak
TLS-RPT Not published
No reporting address, so failed TLS deliveries to this domain go unnoticed by its owner.
Why it scores 59?
- No DMARC record, so receiving servers have no policy to apply to forged mail.
- Accepts mail through 1 MX host.
- No website answers on this domain.
What to publish to close the gaps
The records omen.ru is missing, in the order they are worth doing. Owner names are written out in full, so they work whether your DNS panel wants a full name or a relative one.
Tighten SPF to -all
Nameomen.ruTypeTXTValuev=spf1 <your existing mechanisms> -allKeep the mechanisms you already have and change the final qualifier. Anything softer leaves the forgery path open.
Publish a DMARC record
Start at p=none with a reporting address, read the reports for a few weeks to find the senders you forgot, then move the policy up.
Publish an MTA-STS policy
Name_mta-sts.omen.ruTypeTXTValuev=STSv1; id=<a version string you bump on every change>Serve the policy body at https://mta-sts.omen.ru/.well-known/mta-sts.txt, start it in testing mode, then switch it to enforce so senders refuse to deliver over an unverified connection.
Publish a TLS reporting address
Without it, a sending server that could not negotiate TLS with your mail hosts has nowhere to tell you.
Sign the zone with DNSSEC
Turn DNSSEC on with your DNS provider, then publish the DS record it hands you at your registrar. Every record above is only as trustworthy as the answer that carries it, and signing the zone is what makes the answers verifiable.
Questions about omen.ru
Every answer below is generated from the stored record for this domain.
Is omen.ru a disposable email domain?
Is omen.ru spoofable?
Does omen.ru publish SPF and DMARC?
Who handles email for omen.ru?
How old is the omen.ru domain?
How do I block omen.ru on my signup form?
Can I trust email from omen.ru?
Last verified . We recheck every domain on a schedule, and this report changes only when its records or its verdict do.