kinsta.com

Checked 22 October 2026, 09:32 UTC · via 8.8.8.8
!Passed with warnings
26 passed 5 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.google.com include:servers.mcsv.net ip4:168.245.116.175 include:m.lessonly.com include:6635519.spf04.hubspotemail.net include:stspg-customer.com include:sendgrid.net -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

pass

p=reject (_dmarc.kinsta.com)

Found

Record
v=DMARC1; p=reject; rua=mailto:info@kinsta.com; sp=quarantine
Found at
_dmarc.kinsta.com
TagValueMeaning
vDMARC1Version
prejectPolicy
spquarantineSubdomain policy
ruamailto:info@kinsta.comAggregate report addresses

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:info@kinsta.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

warn

Selectors: k1, s1, s2

Found

Selectors
k1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
k1RSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: k1, s1, s2 #7
    DKIM keys found for this domain with selectors: k1, s1, s2
  • !
    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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mailstream-east.mxrecord.ioA 172.65.213.128no PTR
10mailstream-west.mxrecord.ioA 172.65.220.210no PTR
30mailstream-central.mxrecord.mxA 172.65.64.78no PTR
40mailstream-eu1.mxrecord.ioA 172.65.245.214no PTR

Checks

  • ✓ 4 MX records #9
    Found 4 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: mailstream-east.mxrecord.io, mailstream-west.mxrecord.io, mailstream-central.mxrecord.mx, mailstream-eu1.mxrecord.io
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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: 172.65.213.128 (mailstream-east.mxrecord.io), 172.65.220.210 (mailstream-west.mxrecord.io), 172.65.64.78 (mailstream-central.mxrecord.mx), 172.65.245.214 (mailstream-eu1.mxrecord.io). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mailstream-east.mxrecord.ionone-
mailstream-west.mxrecord.ionone-
mailstream-central.mxrecord.mxnone-
mailstream-eu1.mxrecord.ionone-

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

pass

https://vmc.digicert.com/fc0e73e2-6c47-4d5b-b0ad-0aebbf65e14e.svg

Found

Record
v=BIMI1; l=https://vmc.digicert.com/fc0e73e2-6c47-4d5b-b0ad-0aebbf65e14e.svg; a=https://vmc.digicert.com/fc0e73e2-6c47-4d5b-b0ad-0aebbf65e14e.pem
Found at
default._bimi.kinsta.com
Logo
https://vmc.digicert.com/fc0e73e2-6c47-4d5b-b0ad-0aebbf65e14e.svg
Certificate
https://vmc.digicert.com/fc0e73e2-6c47-4d5b-b0ad-0aebbf65e14e.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/fc0e73e2-6c47-4d5b-b0ad-0aebbf65e14e.svg; certificate: https://vmc.digicert.com/fc0e73e2-6c47-4d5b-b0ad-0aebbf65e14e.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.