monsterenergy.com

Checked 22 October 2026, 09:52 UTC · via 8.8.8.8
!Passed with warnings
27 passed 3 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:103.248.10.126 ip4:103.248.10.127 ip4:135.84.64.0/20 ip4:135.84.68.123/32 ip4:148.105.0.0/16 ip4:148.105.8.0/21 ip4:149.72.126.196/32 ip4:159.135.234.186 ip4:167.89.68.235 ip4:168.245.33.113/32 ip4:168.245.40.179 ip4:168.245.44.5/32 ip4:192.174.82.70/28 ip4:192.185.0.0/24 ip4:198.153.74.0/23 ip4:198.2.128.0/18 ip4:198.207.147.224/27 ip4:198.21.6.113 ip4:199.47.187.110 ip4:199.47.187.111 ip4:204.220.181.148 ip4:204.239.0.224/27 ip4:205.201.128.0/20 ip4:206.152.14.0/24 ip4:208.86.168.0/23 ip4:208.86.170.0/23 ip4:209.208.226.0/23 ip4:216.230.14.224/27 ip4:50.22.105.163/32 ip4:50.97.104.0/24 ip4:50.97.97.0/26 ip4:62.67.54.160/29 ip4:64.18.0.0/20 ip4:64.95.144.196 ip4:74.124.214.198/30 ip4:95.110.198.204/32 include:4b9dd6.workshop-spf.net include:icpbounce.com include:spf.protection.outlook.com exists:%{i}._spf.mta.salesforce.com exists:%{i}.spf.hc5741-64.iphmx.com exists:%{i}.spf.res.cisco.com -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 9 of 10 DNS lookups #2
    SPF record needs 9 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=quarantine (_dmarc.monsterenergy.com)

Found

Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc.reports@Monsterenergy.com; sp=quarantine
Found at
_dmarc.monsterenergy.com
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc.reports@Monsterenergy.comAggregate report addresses

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.reports@Monsterenergy.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

pass

Selectors: s1, s2

Found

Selectors
s1, s2
_domainkey
NOERROR
SelectorKeyFlags
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: s1, s2 #7
    DKIM keys found for this domain with selectors: s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: s1: RSA 2048 bits; s2: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
34505, 2371
Signatures valid until
13 December 2026, 03:48 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-12-13 #21
    DNSKEY signatures are valid until 2026-12-13T03:48:48Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
1mx1.hc5741-64.iphmx.comA 68.232.145.102 A 68.232.157.137esa.hc5741-64.iphmx.com ✓ esa.hc5741-64.iphmx.com ✓
5mx2.hc5741-64.iphmx.comA 68.232.145.102 A 68.232.157.137esa.hc5741-64.iphmx.com ✓ esa.hc5741-64.iphmx.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: mx1.hc5741-64.iphmx.com, mx2.hc5741-64.iphmx.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.hc5741-64.iphmx.comnone-
mx2.hc5741-64.iphmx.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

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