Email Security Analysis of ion.ba

Complete verification of ion.ba's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.

Last updated: April 15, 2026

63C
This domain is vulnerable to spoofing

SPF

Warning
v=spf1 ip4:78.47.23.83 ip4:78.47.23.83 ip4:116.202.131.145 +a +mx ~all
Read the guide

DKIM

OK
Selectors: default, mail

DMARC

Warning
v=DMARC1; p=none; sp=none; rua=mailto:abuse@ion.hosting; pct=100 ;ri=86400; aspf=r; adkim=r; fo=1; ruf=mailto:abuse@ion.hosting; rf=afrf
Read the guide

MX

OK
o4.ionba.com

MTA-STS

Missing

No record found

Read the guide

Recommendations

  1. 1Change your DMARC policy from p=none to p=reject to block spoofing

    With p=none, your DMARC record only monitors — it doesn't actually block spoofed emails. Attackers can still send emails as your domain and they'll be delivered normally. Switching to p=reject instructs receiving servers to drop fraudulent messages before they reach the inbox.

  2. 2Harden your SPF by replacing ~all with -all (hardfail)

    With ~all (softfail), unauthorized senders are flagged but emails are usually still delivered. Switching to -all (hardfail) explicitly tells receiving servers to reject emails from unauthorized sources, providing much stronger protection against spoofing.

  3. 3Add MTA-STS to enforce TLS encryption for incoming emails

    Without MTA-STS, an attacker performing a man-in-the-middle attack can downgrade the connection between mail servers to plaintext, intercepting emails in transit. MTA-STS tells sending servers to only deliver via TLS with a valid certificate, preventing downgrade attacks.

Need help securing your domain?

If you're not sure how to apply these fixes, get in touch and we'll help you out.

Contact us

Run a live analysis

The results above are updated daily. For an instant check of ion.ba, run a live analysis.

Analyze ion.ba live

Guides to understand these results