napaonline.com

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

SPF

pass

SPF record published

Found

Record
v=spf1 mx exists:%{i}.spf.hc3618-75.iphmx.com ip4:208.254.241.0/25 ip4:65.82.138.0/25 ip4:65.203.102.128/25 include:sendgrid.net include:spf.protection.outlook.com ip4:199.96.226.243 ip4:199.96.224.242 ip4:199.96.225.187 ip4:199.96.225.250/31 ip4:199.96.227.38 ip4:199.96.227.41 ~all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 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.napaonline.com)

Found

Record
v=DMARC1; p=none; pct=100; rua=mailto:_demarc@napaonline.com; ruf=mailto:_demarc@napaonline.com; fo=1; adkim=r; aspf=r; rf=afrf; ri=3600; sp=none
Found at
_dmarc.napaonline.com
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:_demarc@napaonline.comAggregate report addresses
rufmailto:_demarc@napaonline.comFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
rfafrfFailure report format
ri3600Report interval (seconds)

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:_demarc@napaonline.com
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector2, s1, s2

Found

Selectors
selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector2RSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector2 (1024 bits), 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

pass

2 mail servers

Found

PriorityHostRecordsReverse DNS
10napaonline-com.mail.protection.outlook.comA 52.101.9.90 A 52.101.194.158 A 52.101.9.93 A 52.101.60.179 AAAA 2a01:111:f403:c903::3 AAAA 2a01:111:f403:c927:: AAAA 2a01:111:f403:c95d:: AAAA 2a01:111:f403:f805::2mail-bl3pr02cu00102.inbound.protection.outlook.com ✓ mail-ch3pr04cu00106.inbound.protection.outlook.com ✓ mail-blapr04cu00105.inbound.protection.outlook.com ✓ mail-bn3pr0301cu00103.inbound.protection.outlook.com ✓ mail-mw2pr02cu00503.inbound.protection.outlook.com ✓ mail-bn6pr21cu00500.inbound.protection.outlook.com ✓ mail-ph8pr05cu00300.inbound.protection.outlook.com ✓ mail-co2pr03cu00202.inbound.protection.outlook.com ✓
20napaonline-com.mail.protection.outlook.comA 52.101.60.173 A 52.101.202.156 A 52.101.194.19 A 52.101.41.21 AAAA 2a01:111:f403:c922:: AAAA 2a01:111:f403:f805::3 AAAA 2a01:111:f403:f913::2 AAAA 2a01:111:f403:f804::7mail-bn3pr0501cu00105.inbound.protection.outlook.com ✓ mail-ph8pr21cu00204.inbound.protection.outlook.com ✓ mail-ch5pr02cu00303.inbound.protection.outlook.com ✓ mail-sj2pr05cu00305.inbound.protection.outlook.com ✓ mail-bl0pr03cu00400.inbound.protection.outlook.com ✓ mail-ea3pr05cu00103.inbound.protection.outlook.com ✓ mail-cy4pr03cu00102.inbound.protection.outlook.com ✓ mail-co2pr03cu00307.inbound.protection.outlook.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 16 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
napaonline-com.mail.protection.outlook.comnone-

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