Email Security Analysis of uic.edu

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

Last updated: April 15, 2026

72B
This domain is protected against spoofing

SPF

Warning
v=spf1 include:spf.uic.edu ip4:192.17.86.0/24 ip4:128.174.180.0/24 ip4:64.22.178.56 ip4:64.22.186.244 include:relays._spf.illinois.edu include:_spf.google.com include:mh.blackboard.com include:spf.protection.outlook.com ~all
Read the guide

DKIM

OK
Selectors: google, selector1, selector2, dkim, mail, s1, s2

DMARC

Warning
v=DMARC1; p=quarantine; fo=0; ri=3600; rua=mailto:52419103f613213@rep.dmarcanalyzer.com, mailto:dmarc-feedback@uic.edu; ruf=mailto:dmarc-feedback@uic.edu
Read the guide

MX

OK
uic-edu.mail.protection.outlook.com

MTA-STS

Missing

No record found

Read the guide

Recommendations

  1. 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.

  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.

Run a live analysis

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

Analyze uic.edu live

Guides to understand these results