SurfaceMap › n › nchem.com

nchem.com

Checked 2026-10-22 10:01 UTC · first added 2026-10-21

✗Problems found Score 30 of 100

Domain & DNS

fail

16 passed 5 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

✗

Nameservers not responding

Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.dns.com.cn (240c:4082:ffff:ff01:0:d:0:34a): read udp [2a01:4f8:1c1c:eebf::1]:34085->[240c:4082:ffff:ff01:0:d:0:34a]:53: i/o timeout; ns2.dns.com.cn (240c:4082:ffff:ff01:0:d:0:69): read udp [2a01:4f8:1c1c:eebf::1]:53424->[240c:4082:ffff:ff01:0:d:0:69]:53: i/o timeout.

#14
✗

No DNS over TCP

Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.dns.com.cn (61.172.183.70): dial tcp 61.172.183.70:53: i/o timeout; ns1.dns.com.cn (61.240.129.114): dial tcp 61.240.129.114:53: i/o timeout; ns13.dns.com.cn (61.172.183.76): dial tcp 61.172.183.76:53: i/o timeout; ns14.dns.com.cn (61.240.129.114): dial tcp 61.240.129.114:53: i/o timeout; ns2.dns.com.cn (61.172.183.76): dial tcp 61.172.183.76:53: i/o timeout; ns2.dns.com.cn (61.240.129.147): dial tcp 61.240.129.147:53: i/o timeout.

#19
!

NS sets differ

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns13.dns.com.cn, ns14.dns.com.cn; only in the zone: ns1.dns.com.cn, ns2.dns.com.cn. ns1.dns.com.cn, ns13.dns.com.cn, ns14.dns.com.cn, ns2.dns.com.cn report NS ns1.dns.com.cn ns2.dns.com.cn.

#7
!

Software version disclosed

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.dns.com.cn: "9.11.0pre-alpha"; ns13.dns.com.cn: "9.11.0pre-alpha"; ns14.dns.com.cn: "9.11.0pre-alpha"; ns2.dns.com.cn: "9.11.0pre-alpha". Hide or replace the version string.

#17
!

No EDNS

Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.dns.com.cn (61.172.183.70), ns13.dns.com.cn (61.172.183.76), ns2.dns.com.cn (61.172.183.76).

#20
!

Unusual SOA timers

SOA · expire 4h is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 4h must be longer than refresh + retry. Current values: refresh 8h, retry 4h, expire 4h, negative TTL 10m.

#23
!

Not signed

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.

#27

Recent checks

✗

Full report

Domain & DNS report for nchem.com ›

Mail

fail

7 passed 5 warn 2 failed

Areas

✗SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

✗

No DMARC record

DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.

#5
✗

No SPF record

SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.

#6
!

No key under common selectors

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

#7
!

Not enabled

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

#8
!

Hosts without IPv6

MX · The following MX hosts could not be resolved to IPv6 addresses: mx11.dns.com.cn

#11
!

Single MX host, no backup

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
!

Not configured

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.

#32

Recent checks

✗

Full report

Mail report for nchem.com ›