myflorida.com

Checked 22 October 2026, 09:54 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 2 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:172.30.5.5 ip4:204.126.116.20 include:spf.protection.outlook.com ~all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 2 of 10 DNS lookups #2
    SPF record needs 2 DNS lookups (limit is 10).
  • ✓ 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.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.myflorida.com)

Found

Record
v=DMARC1; p=none; rua=mailto:DMARCReporting-Aggregate@dms.fl.gov; ruf=mailto:DMARCReporting-Forensic@dms.fl.gov; fo=1
Found at
_dmarc.myflorida.com
External report address
mailto:DMARCReporting-Aggregate@dms.fl.gov (not authorized)
External report address
mailto:DMARCReporting-Forensic@dms.fl.gov (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:DMARCReporting-Aggregate@dms.fl.govAggregate report addresses
rufmailto:DMARCReporting-Forensic@dms.fl.govFailure report addresses
fo1Failure reporting options

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:DMARCReporting-Aggregate@dms.fl.gov
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:DMARCReporting-Aggregate@dms.fl.gov (needs myflorida.com._report._dmarc.dms.fl.gov); mailto:DMARCReporting-Forensic@dms.fl.gov (needs myflorida.com._report._dmarc.dms.fl.gov). Ask the report provider to publish the record, or check the address.
    #29

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.myflorida.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

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

3 mail servers

Found

PriorityHostRecordsReverse DNS
0myflorida-com.mail.protection.outlook.comA 52.101.60.168 A 52.101.41.204 A 52.101.60.145 A 52.101.60.170 AAAA 2a01:111:f403:c803::a AAAA 2a01:111:f403:f90b::5 AAAA 2a01:111:f403:f801::1 AAAA 2a01:111:f403:c927::5mail-bn0pr09cu00100.inbound.protection.outlook.com ✓ mail-byapr09cu00104.inbound.protection.outlook.com ✓ mail-bnypr09cu00101.inbound.protection.outlook.com ✓ mail-bn3pr09cu00102.inbound.protection.outlook.com ✓ mail-bnypr09cu00102.inbound.protection.outlook.com ✓ mail-bn0pr09cu00105.inbound.protection.outlook.com ✓ mail-byapr09cu00101.inbound.protection.outlook.com ✓ mail-bn3pr09cu00105.inbound.protection.outlook.com ✓
10dohsmsi06.doh.state.fl.usA 164.51.255.20dohsmsi06.doh.state.fl.us ✓
10dohsmsi07.doh.state.fl.usA 164.51.255.21dohsmsi07.doh.state.fl.us ✓

Checks

  • ✓ 3 MX records #9
    Found 3 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: dohsmsi06.doh.state.fl.us, dohsmsi07.doh.state.fl.us
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 3 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
myflorida-com.mail.protection.outlook.comnone-
dohsmsi06.doh.state.fl.usnone-
dohsmsi07.doh.state.fl.usnone-

Checks

  • !
    Not configured
    MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

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