themepalace.com

Checked 22 October 2026, 11:02 UTC · via 8.8.8.8
!Passed with warnings
24 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:157.230.80.180 include:emailsrvr.com ~all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.themepalace.com)

Found

Record
v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:47019fc797284bd38f21ef6257f95eca@dmarc-reports.cloudflare.net;
Found at
_dmarc.themepalace.com
External report address
mailto:47019fc797284bd38f21ef6257f95eca@dmarc-reports.cloudflare.net (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
ruamailto:47019fc797284bd38f21ef6257f95eca@dmarc-reports.cloudflare.netAggregate report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF 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:47019fc797284bd38f21ef6257f95eca@dmarc-reports.cloudflare.net
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors
default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits
dkimRSA 1024 bits
mailRSA 1024 bits
emailRSA 1024 bits
k1RSA 1024 bits
selector1RSA 1024 bits
selector2RSA 1024 bits
googleRSA 1024 bits
zohoRSA 1024 bits
mxRSA 1024 bits
keyRSA 1024 bits
mtaRSA 1024 bits
pmRSA 1024 bits
dkim-smtpRSA 1024 bits
s1RSA 1024 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7
    DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), dkim (1024 bits), mail (1024 bits), email (1024 bits), k1 (1024 bits), selector1 (1024 bits), selector2 (1024 bits), google (1024 bits), zoho (1024 bits), mx (1024 bits), key (1024 bits), mta (1024 bits), pm (1024 bits), dkim-smtp (1024 bits), s1 (1024 bits), s2 (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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.emailsrvr.comA 184.106.54.1mx1.emailsrvr.com (does not resolve back)
20mx2.emailsrvr.comA 108.166.43.2mx2.emailsrvr.com (does not resolve back)

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.emailsrvr.com, mx2.emailsrvr.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 does not match
    The PTR name of these addresses does not resolve back to the same address: 184.106.54.1 -> mx1.emailsrvr.com, 108.166.43.2 -> mx2.emailsrvr.com.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.emailsrvr.comnone-
mx2.emailsrvr.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