Email Security Analysis of ctmobi.it
Complete verification of ctmobi.it'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:52.211.11.146 include:_spf.google.com include:amazonses.com include:spf.protection.outlook.com include:_spf.salesforce.com include:3901390.spf07.hubspotemail.net -allDKIM
OKSelectors: google, k1, cmDMARC
OKv=DMARC1;p=reject;sp=reject;pct=100;rua=mailto:dmarc@nextwork360.uriports.com;ruf=mailto:dmarc@nextwork360.uriports.com;ri=86400;aspf=r;adkim=r;fo=0:1:d:sMX
OKaspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.comRecommendations
1Add 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 ctmobi.it, run a live analysis.
Analyze ctmobi.it 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.