linksys.com

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

SPF

fail

SPF record published

Found

Record
v=spf1 ip4:66.35.37.96/27 ip4:54.240.10.84/22 ip4:209.177.160.9/20 ip4:67.202.205.230/27 include:spf.protection.outlook.com include:_spf.salesforce.com include:cust-spf.exacttarget.com include:spf2.linksys.com include:spf.happyfox.com a:production.na01.linksys.demandware.net -all
DNS lookups
12 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    12 DNS lookups, over the limit of 10
    SPF record needs 12 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #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.
  • ✓ 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.linksys.com)

Found

Record
v=DMARC1; p=none; pct=100
Found at
_dmarc.linksys.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: k1

Found

Selectors
k1
_domainkey
NOERROR
SelectorKeyFlags
k1RSA 1024 bits

Checks

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

1 mail server

Found

PriorityHostRecordsReverse DNS
0linksys-com.mail.protection.outlook.comA 52.101.89.2 A 52.101.89.0 A 52.101.99.2 A 52.101.89.18 AAAA 2a01:111:f403:ca0b::2 AAAA 2a01:111:f403:ca1a:: AAAA 2a01:111:f403:ca1a::1 AAAA 2a01:111:f403:ca0b::6mail-lo3p265cu00302.inbound.protection.outlook.com ✓ mail-lo2p265cu02300.inbound.protection.outlook.com ✓ mail-cwxp265cu00502.inbound.protection.outlook.com ✓ mail-lo3p265cu00502.inbound.protection.outlook.com ✓ mail-lo0p265cu00202.inbound.protection.outlook.com ✓ mail-cwxp265cu00500.inbound.protection.outlook.com ✓ mail-cwxp265cu00601.inbound.protection.outlook.com ✓ mail-lo3p265cu00506.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 8 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
linksys-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