SurfaceMap › i › ingramspark.com

ingramspark.com

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

Domain & DNS

warn

22 passed 6 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.lightningsource.com (glue 12.230.218.171, zone 4.37.103.9). Update the glue at your registrar.
    #8
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.lightningsource.com: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; ns2.lightningsource.com: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; ns3.lightningsource.com: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1792641335 on ns3.lightningsource.com (62.105.109.8); 1792641336 on ns1.lightningsource.com (4.37.103.9), ns2.lightningsource.com (198.252.232.11). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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 (30s), MX (30s). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for ingramspark.com ›

Mail

fail

22 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.ingramspark.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.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 ingramspark.com ›