SurfaceMap › t › tenpay.com

tenpay.com

Checked 2026-10-22 11:01 UTC · first added 2026-10-21
✗Problems found Score 42 of 100

Domain & DNS

fail

23 passed 2 warn 2 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns2.qq.com (49.7.250.140): read udp 46.225.38.91:33780->49.7.250.140: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.qq.com (112.90.13.140): dial tcp 112.90.13.140:53: i/o timeout; ns1.qq.com (183.60.116.2): dial tcp 183.60.116.2:53: i/o timeout; ns1.qq.com (2402:4e00:c050:7a00::3): dial tcp [2402:4e00:c050:7a00::3]:53: i/o timeout; ns2.qq.com (1.12.96.10): dial tcp 1.12.96.10:53: i/o timeout; ns2.qq.com (240e:974:e600:3ee::2): dial tcp [240e:974:e600:3ee::2]:53: i/o timeout; ns3.qq.com (120.204.7.98): dial tcp 120.204.7.98:53: i/o timeout.
    #19
  • !
    Unusual SOA timers
    SOA · expire 10m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 10m must be longer than refresh + retry. Current values: refresh 1h, retry 5m, expire 10m, negative TTL 5m.
    #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 tenpay.com ›

Mail

fail

14 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.tenpay.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 IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: mail.tenpay.com, mail2.tenpay.com
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail.tenpay.com, mail2.tenpay.com
    #11
  • !
    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 tenpay.com ›