utsandiego.com

Checked 22 October 2026, 11:20 UTC · via 8.8.8.8
✗Problems found
10 passed 5 warnings 2 failed 2 info

SPF

fail

SPF record published

Found

Record
v=spf1 include:spf.tronc.com include:sosdmail.com include:spf.imshopping.net include:adicio.com include:outlook.com include:spf.protection.outlook.com ~all
DNS lookups
15 of 10
Void lookups
2 of 2
Problem
include:spf.imshopping.net does not exist or has no records
Problem
include:adicio.com does not exist or has no records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    15 DNS lookups, over the limit of 10
    SPF record needs 15 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record. Problems found: include:spf.imshopping.net does not exist or has no records; include:adicio.com does not exist or has no records.
    #2
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • !
    2 void lookups
    2 include/redirect targets does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.utsandiego.com)

Found

Record
v=DMARC1;p=none;pct=100
Found at
_dmarc.utsandiego.com
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

DKIM

warn

Selectors: google, s1, s2

Found

Selectors
google, s1, s2
_domainkey
NXDOMAIN
SelectorKeyFlags
googleRSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: google, s1, s2 #7
    DKIM keys found for this domain with selectors: google, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

No MX records found

Checks

  • !
    No MX records
    No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9
  • i
    Receives no mail but sends
    The domain has no MX records but its SPF record authorizes senders. If it does not send mail either, use "v=spf1 -all" and DMARC p=reject.
    #28

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38