SurfaceMap › j › jirenjituan.com

jirenjituan.com

Checked 2026-10-22 09:24 UTC · first added 2026-10-21

✗Problems found Score 50 of 100

Domain & DNS

fail

22 passed 4 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

✗

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.35.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns1.35.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns2.35.net (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns2.35.net (61.172.183.73): dial tcp 61.172.183.73:53: i/o timeout; ns2.35.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout; ns3.35.net (118.123.249.114): dial tcp 118.123.249.114:53: i/o timeout; ns3.35.net (61.172.183.77): dial tcp 61.172.183.77:53: i/o timeout; ns3.35.net (240e:d9:c200::2): dial tcp [240e:d9:c200::2]:53: i/o timeout; ns4.35.net (211.149.230.100): dial tcp 211.149.230.100:53: i/o timeout; ns4.35.net (240e:d9:c200:1::2): dial tcp [240e:d9:c200:1::2]:53: i/o timeout.

#19
!

Software version disclosed

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.35.net: "v1.1"; ns2.35.net: "v1.1"; ns3.35.net: "v1.1"; ns4.35.net: "v1.1". 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: ns2.35.net (61.172.183.73), ns3.35.net (61.172.183.77).

#20
!

Serials differ

SOA · The nameservers serve different versions of the zone: 2026042607 on ns2.35.net (61.172.183.73), ns2.35.net (240e:d9:c200:1::2), ns3.35.net (61.172.183.77), ns4.35.net (240e:d9:c200:1::2); 2026042608 on ns1.35.net (118.123.253.132), ns1.35.net (118.123.249.114), ns1.35.net (60.247.150.254), ns1.35.net (240e:d9:c200::2), ns2.35.net (211.149.230.100), ns3.35.net (118.123.249.114), ns3.35.net (240e:d9:c200::2), ns4.35.net (118.123.253.132), ns4.35.net (211.149.230.100). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

#22
!

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 jirenjituan.com ›

Mail

fail

17 passed 6 warn 1 failed

Areas

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

Problems

✗

Policy: none (monitoring only)

DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
!

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: mxbiz1.qq.com, mxbiz2.qq.com

#11
!

No aggregate reports (rua)

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
!

Addresses without reverse DNS

MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 103.86.78.2 (mxbiz1.qq.com), 103.86.78.3 (mxbiz1.qq.com), 43.154.252.16 (mxbiz2.qq.com), 43.154.252.202 (mxbiz2.qq.com). Ask your hosting provider to set one.

#30
!

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 jirenjituan.com ›