SurfaceMap › q › qianlong.com

qianlong.com

Checked 2026-10-22 10:23 UTC · first added 2026-10-21
✗Problems found Score 39 of 100

Domain & DNS

fail

20 passed 3 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.jdgslb.com (183.134.18.116): read udp 46.225.38.91:40072->183.134.18.116:53: i/o timeout; ns2.jdgslb.com (116.196.126.17): read udp 46.225.38.91:59260->116.196.126.17:53: i/o timeout; ns2.jdgslb.com (116.198.195.7): read udp 46.225.38.91:49165->116.198.195.7:53: i/o timeout; ns2.jdgslb.com (114.67.160.149): read udp 46.225.38.91:50928->114.67.160.149: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: freens1.jdgslb.com (183.134.18.114): dial tcp 183.134.18.114:53: i/o timeout; freens1.jdgslb.com (2403:1ec0:1600:ff07::53): dial tcp [2403:1ec0:1600:ff07::53]:53: i/o timeout; freens2.jdgslb.com (183.134.18.115): dial tcp 183.134.18.115:53: i/o timeout; freens2.jdgslb.com (2403:1ec0:1600:ff07::54): dial tcp [2403:1ec0:1600:ff07::54]:53: i/o timeout; ns1.jdgslb.com (2403:1ec0:1600:ff07::153): dial tcp [2403:1ec0:1600:ff07::153]:53: i/o timeout; ns2.jdgslb.com (183.134.18.117): dial tcp 183.134.18.117:53: i/o timeout; ns2.jdgslb.com (2403:1ec0:1600:ff07::154): dial tcp [2403:1ec0:1600:ff07::154]: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: freens1.jdgslb.com, freens2.jdgslb.com; only in the zone: ns1.jdgslb.com, ns2.jdgslb.com. freens1.jdgslb.com, freens2.jdgslb.com, ns1.jdgslb.com, ns2.jdgslb.com report NS ns1.jdgslb.com ns2.jdgslb.com.
    #7
  • !
    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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (2m), AAAA (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 30m; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for qianlong.com ›

Mail

fail

15 passed 4 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 DKIM keys published
    DKIM · _domainkey.qianlong.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #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
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 103.86.78.3 (mxbiz1.qq.com), 103.86.78.2 (mxbiz1.qq.com), 43.154.252.202 (mxbiz2.qq.com), 43.154.252.16 (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 qianlong.com ›