Mail domain report: influencermarketinghub.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:23.101.198.154 ip4:23.101.203.117 ip4:23.101.204.168 ip4:23.101.205.109 ip4:23.101.207.119 include:_spf.google.com include:_spf.reply.io include:servers.mcsv.net include:_spf.firebasemail.com ~all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 7 of 10 DNS lookups #2

SPF record needs 7 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.influencermarketinghub.com)

Found

Record: v=DMARC1; p=none; rua=mailto:76e39f6ad3774855bbd407f6ebda7e26@dmarc-reports.cloudflare.net
Found at: _dmarc.influencermarketinghub.com
External report address: mailto:76e39f6ad3774855bbd407f6ebda7e26@dmarc-reports.cloudflare.net (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:76e39f6ad3774855bbd407f6ebda7e26@dmarc-reports.cloudflare.net	Aggregate report addresses

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:76e39f6ad3774855bbd407f6ebda7e26@dmarc-reports.cloudflare.net
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1

Found

Selectors: k1
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 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

5 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1b	rd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
5	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10	alt3.aspmx.l.googlemail.com	(does not resolve)
10	alt4.aspmx.l.googlemail.com	(does not resolve)

Checks

✓ 5 MX records #9

Found 5 MX records for this domain.
!

Hosts without IP addresses

The following MX hosts could not be resolved to IP addresses: alt3.aspmx.l.googlemail.com, alt4.aspmx.l.googlemail.com

#10
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: alt3.aspmx.l.googlemail.com, alt4.aspmx.l.googlemail.com

#11
✓ Redundant MX hosts #12

Found 5 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 5 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 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.googlemail.com	none	-
alt4.aspmx.l.googlemail.com	none	-

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