SurfaceMap › h › htc.com

htc.com

Checked 2026-10-22 09:13 UTC · first added 2026-10-21
✗Problems found Score 60 of 100

Domain & DNS

fail

22 passed 4 warn 1 failed

Areas

iRegistration ✗Delegation !Nameservers iSOA !DNSSEC !Records

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): 184.85.248.67, 193.108.91.244, 2.16.130.64, 23.211.133.66, 23.211.61.67, 95.100.168.65.
    #9
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: a1-244.akam.net, a22-67.akam.net, a24-64.akam.net, a5-65.akam.net, a6-66.akam.net, a9-67.akam.net; only in the zone: 184.85.248.67, 193.108.91.244, 2.16.130.64, 23.211.133.66, 23.211.61.67, 95.100.168.65. a1-244.akam.net, a22-67.akam.net, a24-64.akam.net, a5-65.akam.net, a6-66.akam.net, a9-67.akam.net report NS 184.85.248.67 193.108.91.244 2.16.130.64 23.211.133.66 23.211.61.67 95.100.168.65.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-244.akam.net: "41824.9"; a1-244.akam.net: "41824.7"; a22-67.akam.net: "48878.31"; a22-67.akam.net: "48878.26"; a24-64.akam.net: "48878.30"; a24-64.akam.net: "48878.27"; a5-65.akam.net: "41824.6"; a5-65.akam.net: "41824.8"; a6-66.akam.net: "48878.32"; a9-67.akam.net: "41824.8"; a9-67.akam.net: "41824.6". Hide or replace the version string.
    #17
  • !
    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 (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 12h; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for htc.com ›

Mail

warn

22 passed 6 warn 0 failed

Areas

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

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector2 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.137.2 (htc-com.mail.protection.outlook.com), 2a01:111:f403:cc09::1 (htc-com.mail.protection.outlook.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 htc.com ›