Email Security Analysis of ccbg.com
Complete verification of ccbg.com's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.
Last updated: April 15, 2026
SPF
Warningv=spf1 include:_spf.google.com include:_spf1.mailgun.org include:_spf2.mailgun.org include:_spf.eu.mailgun.org include:spfhost.messageprovider.com include:_spf.salesforce.com ip4:68.232.131.237 ip4:68.232.137.69 ip4:68.232.141.148 ip4:209.10.132.208 ip4:209.65.253.235 ip4:34.215.165.231 ip4:209.34.255.250 ip4:209.34.255.251 ip4:128.136.104.250 ip4:199.30.234.56/29 ip4:74.203.184.208/30 ip4:199.30.234.64/26 ip4:199.30.234.192/27 ip4:74.203.184.32/27 ip4:207.195.176.0/20 ip4:35.80.141.6 ip4:44.229.121.55 ip4:209.182.248.78 ip4:209.182.249.78 ip4:216.116.80.0/24 ip4:216.116.81.88 ip4:216.116.87.0/24 ip4:74.200.60.0/24 ip4:74.200.63.0/24 ip4:216.116.95.0/24 ip4:52.128.98.34 ip4:52.128.98.35 ip4:52.128.98.36 ip4:67.210.88.16 ip4:54.235.79.89 ip4:23.20.119.18 ip4:148.59.100.16/28 ip4:208.86.168.7 ip4:208.84.65.109 ip4:208.86.201.107 ip4:135.84.68.123 ip4:135.84.79.54 ~allDKIM
OKSelectors: s1, s2DMARC
Warningv=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc@ccbg.com; ruf=mailto:dmarcfailurereports@ccbg.comMX
OKemailpoint1.ccbg.comRecommendations
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.
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.
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.
Run a live analysis
The results above are updated daily. For an instant check of ccbg.com, run a live analysis.
Analyze ccbg.com 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.