SurfaceMap › i › intercontinental.com

intercontinental.com

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

Domain & DNS

warn

22 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: a28-64.akam.net; only in the zone: a4-64.akam.net. a1-131.akam.net, a16-66.akam.net, a26-67.akam.net, a28-64.akam.net, a4-64.akam.net, a5-65.akam.net, a9-66.akam.net report NS a1-131.akam.net a16-66.akam.net a26-67.akam.net a4-64.akam.net a5-65.akam.net a9-66.akam.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-131.akam.net: "41824.6"; a1-131.akam.net: "41824.9"; a16-66.akam.net: "48878.27"; a26-67.akam.net: "48878.27"; a26-67.akam.net: "48878.26"; a28-64.akam.net: "48878.32"; a28-64.akam.net: "48878.31"; a4-64.akam.net: "48878.33"; a4-64.akam.net: "48878.29"; a5-65.akam.net: "41824.7"; a5-65.akam.net: "41824.8"; a9-66.akam.net: "41824.8"; a9-66.akam.net: "41824.4". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 28d, negative TTL 2d.
    #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
  • !
    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 10m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for intercontinental.com ›

Mail

fail

20 passed 4 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: mxa-0036c501.gslb.pphosted.com, mxb-0036c501.gslb.pphosted.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 intercontinental.com ›