Running diagnostic
Running your DNS diagnostic…
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Checking SPF, DMARC, DKIM, MX, DNS, blacklists and domain & SSL expiry. A domain we haven't scanned before takes a few seconds — hang tight.
Scanned Aug 26, 2026 23:27 UTC · 7 checks · public report
Solid base — two policy steps remain.
sc.edu publishes DMARC with p=none — spoofed mail is monitored but not blocked.
Your SPF setup is already close to the DNS lookup limit, with 9 of the 10 allowed checks used. This matters because if you add more mail-sending services later, the SPF check can start failing or become unreliable, which can hurt email delivery and make spoofed mail harder to spot. The fix is to simplify the SPF setup by reducing lookups, usually by removing unnecessary includes or replacing them with a more direct allowlist of the servers you actually use.
v=spf1 ip4:129.252.0.0/16 ip4:184.73.24.220 include:_spft.sc.edu -allYour domain has DMARC set up, but it is only in monitoring mode, so it is not actively blocking spoofed or fake email. This matters because attackers can still send mail that appears to come from your domain, which can hurt trust and increase phishing risk. The fix is to change DMARC from monitoring-only to an enforcement mode so receiving mail servers are told what to do with messages that fail authentication.
v=DMARC1; p=none; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]; fo=1;One send: the full report — every finding and fix — lands in your inbox, with a free account waiting. Opening it signs you in and starts a 14-day Monitor trial. No card, and you can unsubscribe in one click.
Domain owner? Re-scan any time — or email [email protected] to have this page removed.
_dmarc · Record type: TXT · TTL: 3600v=DMARC1; p=quarantine; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]; fo=1; np=reject