kakao.com

Checked 22 October 2026, 09:31 UTC · via 8.8.8.8
✗Problems found
20 passed 6 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:103.246.58.76 ip4:103.246.58.77 ip4:103.246.58.78 ip4:103.246.58.79 ip4:103.246.58.61 ip4:103.246.58.62 ip4:103.246.58.63 ip4:103.246.58.64 ip4:103.246.58.65 include:_spf.daum.net include:_spf.kakao.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.kakao.com)

Found

Record
v=DMARC1; p=none; rua=mailto:dmarc_reports@kakaocorp.com
Found at
_dmarc.kakao.com
External report address
mailto:dmarc_reports@kakaocorp.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:dmarc_reports@kakaocorp.comAggregate report addresses

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc_reports@kakaocorp.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: default

Found

Selectors
default
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bitstest mode (t=y)

Checks

  • ✓ Keys found: default #7
    DKIM keys found for this domain with selectors: default
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    These keys have t=y, so receivers treat DKIM failures as a test: default. Remove t=y once DKIM works.
    #24

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
10mx1.kakao.comA 211.249.219.44no PTR
10mx2.kakao.comA 211.183.209.53no PTR
10mx3.kakao.comA 121.53.85.40no PTR
10mx4.kakao.comA 211.183.210.53no 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: mx1.kakao.com, mx2.kakao.com, mx3.kakao.com, mx4.kakao.com
    #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: 211.249.219.44 (mx1.kakao.com), 211.183.209.53 (mx2.kakao.com), 121.53.85.40 (mx3.kakao.com), 211.183.210.53 (mx4.kakao.com). 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
mx1.kakao.comnone-
mx2.kakao.comnone-
mx3.kakao.comnone-
mx4.kakao.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