iubenda.com

Checked 22 October 2026, 09:22 UTC · via 8.8.8.8
!Passed with warnings
24 passed 7 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a ip4:23.253.182.122 ip4:159.112.245.91 include:144191059.spf08.hubspotemail.net include:_spf.freshsales.io include:spf.spamfilter.io include:spf.protection.outlook.com include:spf-eu.emailsignatures365.com ~all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

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

warn

p=reject (_dmarc.iubenda.com)

Found

Record
v=DMARC1; p=reject; pct=100; rua=mailto:re+hinwrmqwwbe@dmarc.postmarkapp.com; sp=none; aspf=r;
Found at
_dmarc.iubenda.com
External report address
mailto:re+hinwrmqwwbe@dmarc.postmarkapp.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:re+hinwrmqwwbe@dmarc.postmarkapp.comAggregate report addresses
aspfrSPF alignment (r = relaxed, s = strict)

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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:re+hinwrmqwwbe@dmarc.postmarkapp.com
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: default, selector1, google, mx, pm

Found

Selectors
default, selector1, google, mx, pm
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits
selector1RSA 2048 bits
googleRSA 1024 bits
mxRSA 1024 bits
pmRSA 1024 bits

Checks

  • ✓ Keys found: default, selector1, google, mx, pm #7
    DKIM keys found for this domain with selectors: default, selector1, google, mx, pm
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), google (1024 bits), mx (1024 bits), pm (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
1mx.spamfilter.ioA 89.188.78.64 A 46.36.212.38 A 46.36.212.36 A 46.36.212.37 A 89.188.78.65 A 89.188.78.66 A 46.36.212.34 A 94.231.106.12node3.spamfilter.io ✓ node7.spamfilter.io ✓ node8.spamfilter.io ✓ node6.spamfilter.io ✓ node9.spamfilter.io ✓ node10.spamfilter.io ✓ node4.spamfilter.io ✓ node2.spamfilter.io ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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: mx.spamfilter.io
    #11
  • !
    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 1 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx.spamfilter.io3 1 1 9a25f05f2e322dab…Yes

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
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • ✓ DANE on all MX hosts #36
    All 1 MX host publish DNSSEC-validated TLSA records.

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