Mail domain report: thenextweb.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:amazonses.com ~all
DNS lookups: 2 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

Found

Record: v=DMARC1; p=none; np=quarantine; rua=mailto:rrwiwsx3hh@rua.powerdmarc.com; ruf=mailto:rrwiwsx3hh@ruf.powerdmarc.com; fo=1;
Found at: _dmarc.thenextweb.com
External report address: mailto:rrwiwsx3hh@rua.powerdmarc.com (authorized)
External report address: mailto:rrwiwsx3hh@ruf.powerdmarc.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:rrwiwsx3hh@rua.powerdmarc.com	Aggregate report addresses
ruf	mailto:rrwiwsx3hh@ruf.powerdmarc.com	Failure report addresses
fo	1	Failure reporting options
np	quarantine

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:rrwiwsx3hh@rua.powerdmarc.com
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: google

Found

Selectors: google
_domainkey: NOERROR

Selector	Key	Flags
google	RSA 2048 bits

Checks

✓ Keys found: google #7

DKIM keys found for this domain with selectors: google
✓ Strong keys #23

DKIM keys are strong enough: google: RSA 2048 bits.
✓ 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

Priority	Host	Records	Reverse DNS
1	smtp.google.com	A 142.251.127.27 A 142.251.127.26 AAAA 2a00:1450:4001:c21::1b AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓

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

TLS

warn

MTA-STS testing · TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record: v=STSv1; id=20261019124426721590;
Policy URL: https://mta-sts.thenextweb.com/.well-known/mta-sts.txt
Mode: testing
Allowed MX: smtp.google.com
Max age: 86400 seconds
TLS-RPT record: v=TLSRPTv1;rua=mailto:rrwiwsx3hh@tls.powerdmarc.com

DANE (TLSA records)

MX host	TLSA	DNSSEC
smtp.google.com	none	-

Checks

✓ Record published #32

MTA-STS record found with id 20261019124426721590.
!

Policy in testing mode

With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

#33
✓ All MX hosts covered #34

Every MX host matches an mx: line of the MTA-STS policy.
✓ Reports enabled #35

TLS reports are sent to: mailto:rrwiwsx3hh@tls.powerdmarc.com
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