razerzone.com

Checked 22 October 2026, 10:25 UTC · via 8.8.8.8
✗Problems found
19 passed 6 warnings 3 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 mx ip4:121.200.253.195/26 include:messaging-master.com include:amazonses.com include:spf.dynect.net include:spf.mtasv.net include:spf.protection.outlook.com include:spf.sendcloud.org include:salesforce.com -all
DNS lookups
15 of 10
Void lookups
1 of 2
Records published
3
Problem
include:messaging-master.com does not exist or has no records

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    15 DNS lookups, over the limit of 10
    SPF record needs 15 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record. Problems found: include:messaging-master.com does not exist or has no records.
    #2
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✗
    Multiple SPF records
    Found 3 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.
    #16
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • !
    1 void lookup
    1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=reject (_dmarc.razerzone.com)

Found

Record
v=DMARC1; p=reject
Found at
_dmarc.razerzone.com
TagValueMeaning
vDMARC1Version
prejectPolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.

DKIM

fail

Selectors: default, k1, selector2, pm

Found

Selectors
default, k1, selector2, pm
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 768 bits
k1RSA 1024 bits
selector2RSA 1024 bits
pmRSA 768 bits

Checks

  • ✓ Keys found: default, k1, selector2, pm #7
    DKIM keys found for this domain with selectors: default, k1, selector2, pm
  • ✗
    Weak DKIM key
    RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): default (768 bits), pm (768 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
0razerzone-com.mail.protection.outlook.comA 52.101.157.80 A 52.101.137.0 A 52.101.137.2 A 52.101.124.117 AAAA 2a01:111:f403:cc1f::4 AAAA 2a01:111:f403:cc1a::8 AAAA 2a01:111:f403:cc09::1 AAAA 2a01:111:f403:cc09::mail-os8pr02cu00100.inbound.protection.outlook.com ✓ mail-sg2pr03cu00500.inbound.protection.outlook.com ✓ no PTR mail-tydpr03cu00105.inbound.protection.outlook.com ✓ mail-os8pr02cu00104.inbound.protection.outlook.com ✓ mail-tydpr03cu00100.inbound.protection.outlook.com ✓ no PTR mail-sg2pr03cu00500.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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (razerzone-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (razerzone-com.mail.protection.outlook.com). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
razerzone-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

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