ktvz.com

Checked 22 October 2026, 09:33 UTC · via 8.8.8.8
✗Problems found
18 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:20.97.70.227/32 ip4:20.98.2.159/32 ip4:20.98.33.77/32 ip4:40.124.2.148/32 ip4:52.240.209.173/32 ip4:52.252.238.67/32 ip4:65.98.146.0/24 ip4:65.98.206.0/24 ip4:65.98.214.0/24 ip4:65.98.228.0/24 ip4:65.98.250.0/24 ip4:69.63.150.0/23 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:185.131.228.0/24 ip4:185.131.229.0/25 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.24.224.0/20 ip4:216.27.8.32/28 ip4:216.27.12.144/28 ip4:216.27.14.0/26 ip4:216.27.14.64/27 ip4:216.27.20.128/27 ip4:216.27.22.160/27 ip4:216.27.22.192/27 ip4:216.198.0.0/18 include:secondstreetmail.com include:us._netblocks.mimecast.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.ktvz.com)

Found

Record
v=DMARC1; p=none;
Found at
_dmarc.ktvz.com
TagValueMeaning
vDMARC1Version
pnonePolicy

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.
  • !
    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

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

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
0us-smtp-inbound-1.mimecast.comA 170.10.132.221 A 170.10.128.221 A 170.10.132.242 A 170.10.128.141 A 170.10.128.242 A 170.10.132.141us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-2.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-2.mimecast.com ✓
0us-smtp-inbound-2.mimecast.comA 170.10.132.141 A 170.10.132.242 A 170.10.132.221 A 170.10.128.141 A 170.10.128.242 A 170.10.128.221us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.com ✓ us-smtp-inbound-1.mimecast.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: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.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 12 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
us-smtp-inbound-1.mimecast.comnone-
us-smtp-inbound-2.mimecast.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