Email Security Analysis of vrh.ba
Complete verification of vrh.ba's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.
Last updated: April 15, 2026
SPF
OKv=spf1 ip4:185.99.0.235 ip4:185.99.0.240 ip4:185.99.0.242 ip4:185.99.0.247 ip4:185.99.0.248 ip6:2a00:8620::/32 -allDKIM
OKSelectors: defaultDMARC
Warningv=DMARC1;p=quarantine;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:admin@vrh.ba;ruf=mailto:admin@vrh.baMX
OKvrh.baRecommendations
1Upgrade your DMARC policy from p=quarantine to p=reject for full blocking
With p=quarantine, spoofed emails are sent to spam instead of being blocked outright. Some recipients still check spam folders, and sophisticated attacks can be flagged as legitimate by users. p=reject ensures fraudulent emails never reach any folder.
2Add 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.
Run a live analysis
The results above are updated daily. For an instant check of vrh.ba, run a live analysis.
Analyze vrh.ba liveGuides to understand these results
SPF Guide
Understand how SPF defines which servers are authorized to send emails for a domain.
DKIM Guide
Discover how DKIM cryptographically signs your emails to guarantee their authenticity.
DMARC Guide
Learn how DMARC orchestrates SPF and DKIM to protect your domain.
MTA-STS Guide
Learn how MTA-STS enforces TLS encryption to protect your emails in transit.
SPF vs DKIM vs DMARC
Compare the three protocols and understand how they work together.