skhynix.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns.skhynix.com; only in the zone: ns.hynix.com. ns.hynix.com, ns.skhynix.com report NS ns.hynix.com.

Delegation · all IPv4 addresses are in 166.125.250.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

SOA · retry 1h should be shorter than refresh 1h; expire 3d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 1h, expire 3d, negative TTL 12h.

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

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

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · 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

DMARC · 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.

MX · 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.

TLS · 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.