SurfaceMap › t › tajhotels.com

tajhotels.com

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

Domain & DNS

warn

30 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA ✓DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-240.akam.net: "41824.11"; a11-65.akam.net: "41824.9"; a11-65.akam.net: "41824.5"; a13-64.akam.net: "41824.5"; a13-64.akam.net: "41824.10"; a22-67.akam.net: "48878.33"; a22-67.akam.net: "48878.29"; a24-65.akam.net: "48878.27"; a24-65.akam.net: "48878.30"; a4-65.akam.net: "48878.29". Hide or replace the version string.
    #17
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 8m20s; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for tajhotels.com ›

Mail

fail

24 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    11 DNS lookups, over the limit of 10
    SPF · SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: tajhotels-com.mail.protection.outlook.com
    #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
  • !
    Signatures expire in 69h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-25T07:44:11Z (in 69h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 tajhotels.com ›