llbean.com

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

SPF

fail

SPF record published

Found

Record
v=spf1 include:spftext.egain.cloud include:spf.protection.outlook.com ip4:66.128.144.88/29 ip4:103.2.140.0/22 ip4:103.36.108.0/22 ip4:103.47.204.0/22 ip4:43.228.184.0/22 ip4:216.22.15.224/27 ip4:207.58.147.64/28 ip4:207.58.142.208/29 ip4:198.2.177.0/24 ip4:198.2.178.0/24 ip4:198.2.179.0/24 ip4:198.2.180.0/24 ip4:205.201.139.0/24 ip4:205.201.136.0/23 ip4:205.201.134.128/25 ip4:205.201.131.128/25 ip4:198.2.186.0/23 ip4:66.165.105.241/29 ip4:66.165.105.248 ip4:216.151.52.100 ip4:208.50.138.11 ip4:64.211.226.48 ip4:162.247.216.0/22 ip4:139.60.152.0/22 ip4:54.186.193.102/32 ip4:52.222.73.120/32 ip4:52.222.73.83/32 ip4:52.222.62.51/32 ip4:52.222.75.85/32 ip4:198.2.128.0/24 ip4:198.2.132.0/22 ip4:198.2.136.0/23 include:_spf.atoracle.com a:production.shop.llbean.demandware.net include:spf.mandrillapp.com a:production.na04.llbean.demandware.net a:staging.na04.llbean.demandware.net include:mailgun.org include:everbridge.net ~all
DNS lookups
19 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    19 DNS lookups, over the limit of 10
    SPF record needs 19 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

warn

p=quarantine (_dmarc.llbean.com)

Found

Record
v=DMARC1; p=quarantine; sp=quarantine; adkim=r; aspf=r; pct=100; fo=1; rua=mailto:dmarc_rua@llbean.com; ruf=mailto:dmarc_ruf@llbean.com
Found at
_dmarc.llbean.com
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc_rua@llbean.comAggregate report addresses
rufmailto:dmarc_ruf@llbean.comFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc_rua@llbean.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1, s1, s2

Found

Selectors
selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

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

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0llbean-com.mail.protection.outlook.comA 52.101.10.16 A 52.101.60.188 A 52.101.41.24 A 52.101.60.65 AAAA 2a01:111:f403:c902::16 AAAA 2a01:111:f403:c918:: AAAA 2a01:111:f403:c936::1 AAAA 2a01:111:f403:c922::4mail-bn6pr21cu00500.inbound.protection.outlook.com ✓ mail-bn0pr04cu01004.inbound.protection.outlook.com ✓ mail-sj0pr03cu01600.inbound.protection.outlook.com ✓ mail-bn3pr02cu00101.inbound.protection.outlook.com ✓ mail-byapr04cu00306.inbound.protection.outlook.com ✓ mail-byapr04cu00400.inbound.protection.outlook.com ✓ mail-cy4pr03cu00201.inbound.protection.outlook.com ✓ mail-bl1pr02cu00104.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
llbean-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

pass

https://vmc.digicert.com/cee1e5d4-ec1f-471e-8c7a-061f08891930.svg

Found

Record
v=BIMI1;l=https://vmc.digicert.com/cee1e5d4-ec1f-471e-8c7a-061f08891930.svg;a=https://vmc.digicert.com/cee1e5d4-ec1f-471e-8c7a-061f08891930.pem
Found at
default._bimi.llbean.com
Logo
https://vmc.digicert.com/cee1e5d4-ec1f-471e-8c7a-061f08891930.svg
Certificate
https://vmc.digicert.com/cee1e5d4-ec1f-471e-8c7a-061f08891930.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/cee1e5d4-ec1f-471e-8c7a-061f08891930.svg; certificate: https://vmc.digicert.com/cee1e5d4-ec1f-471e-8c7a-061f08891930.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.