littelfuse.com

Checked 22 October 2026, 09:40 UTC · via 8.8.8.8
✗Problems found
20 passed 5 warnings 1 failed 4 info

SPF

info

SPF record published

Found

Record
v=spf1 redirect=littelfuse.com.hosted.spf-report.com
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 3 of 10 DNS lookups #2
    SPF record needs 3 DNS lookups (limit is 10).
  • i
    Delegated via redirect
    SPF record has no 'all' mechanism but redirects to littelfuse.com.hosted.spf-report.com, whose policy applies.
    #3
  • ✓ 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.littelfuse.com)

Found

Record
v=DMARC1; p=none; rua=mailto:o365alerts@littelfuse.com,mailto:littelfuse@rua.netcraft.com,mailto:42dfbb60@mxtoolbox.dmarc-report.com; ruf=mailto:o365alerts@littelfuse.com,mailto:littelfuse@ruf.netcraft.com,mailto:42dfbb60@forensics.dmarc-report.com; fo=1
Found at
_dmarc.littelfuse.com
External report address
mailto:littelfuse@rua.netcraft.com (authorized)
External report address
mailto:42dfbb60@mxtoolbox.dmarc-report.com (authorized)
External report address
mailto:littelfuse@ruf.netcraft.com (authorized)
External report address
mailto:42dfbb60@forensics.dmarc-report.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:o365alerts@littelfuse.com,mailto:littelfuse@rua.netcraft.com,mailto:42dfbb60@mxtoolbox.dmarc-report.comAggregate report addresses
rufmailto:o365alerts@littelfuse.com,mailto:littelfuse@ruf.netcraft.com,mailto:42dfbb60@forensics.dmarc-report.comFailure 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:o365alerts@littelfuse.com, mailto:littelfuse@rua.netcraft.com, mailto:42dfbb60@mxtoolbox.dmarc-report.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector2, s1, s2

Found

Selectors
selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector2RSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 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). 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

4 mail servers

Found

PriorityHostRecordsReverse DNS
5mailstream-eu1.mxrecord.ioA 172.65.245.214no PTR
10mailstream-central.mxrecord.mxA 172.65.64.78no PTR
20mailstream-east.mxrecord.ioA 172.65.213.128no PTR
20mailstream-west.mxrecord.ioA 172.65.220.210no PTR

Checks

  • ✓ 4 MX records #9
    Found 4 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: mailstream-eu1.mxrecord.io, mailstream-central.mxrecord.mx, mailstream-east.mxrecord.io, mailstream-west.mxrecord.io
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 172.65.245.214 (mailstream-eu1.mxrecord.io), 172.65.64.78 (mailstream-central.mxrecord.mx), 172.65.213.128 (mailstream-east.mxrecord.io), 172.65.220.210 (mailstream-west.mxrecord.io). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mailstream-eu1.mxrecord.ionone-
mailstream-central.mxrecord.mxnone-
mailstream-east.mxrecord.ionone-
mailstream-west.mxrecord.ionone-

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