skhynix.com

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

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:166.125.252.71 ip4:166.125.252.73 ip4:166.125.252.76 ip4:166.125.252.79 ip4:166.125.252.85 ip4:166.125.252.90 ip4:166.125.252.92 include:_spfblocka.toast.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

fail

p=none (_dmarc.skhynix.com)

Found

Record
v=DMARC1;p=none;sp=quarantine;pct=100;rua=mailto:skhynix@ipartners.co.kr;
Found at
_dmarc.skhynix.com
External report address
mailto:skhynix@ipartners.co.kr (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:skhynix@ipartners.co.krAggregate 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:skhynix@ipartners.co.kr
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:skhynix@ipartners.co.kr (needs skhynix.com._report._dmarc.ipartners.co.kr). Ask the report provider to publish the record, or check the address.
    #29

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

5 mail servers

Found

PriorityHostRecordsReverse DNS
0antispam.skhynix.comA 166.125.252.130no PTR
10vmail.skhynix.comA 166.125.252.80vmail.skhynix.com ✓
20invmail.skhynix.comA 166.125.252.78invmail.skhynix.com ✓
40invmail3.skhynix.comA 166.125.252.89invmail3.skhynix.com ✓
50invmail4.skhynix.comA 166.125.252.91invmail4.skhynix.com ✓

Checks

  • ✓ 5 MX records #9
    Found 5 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: antispam.skhynix.com, vmail.skhynix.com, invmail.skhynix.com, invmail3.skhynix.com, invmail4.skhynix.com
    #11
  • ✓ Redundant MX hosts #12
    Found 5 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 5 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: 166.125.252.130 (antispam.skhynix.com). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
antispam.skhynix.comnone-
vmail.skhynix.comnone-
invmail.skhynix.comnone-
invmail3.skhynix.comnone-
invmail4.skhynix.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