SurfaceMap › n › ning.com

ning.com

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

Domain & DNS

warn

25 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.ning.com: "9.10.3-P4-Ubuntu"; ns2.ning.com: "9.10.3-P4-Ubuntu". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2 on ns-1132.awsdns-13.org (205.251.196.108), ns-1132.awsdns-13.org (2600:9000:5304:6c00::1), ns-1707.awsdns-21.co.uk (205.251.198.171), ns-1707.awsdns-21.co.uk (2600:9000:5306:ab00::1), ns-385.awsdns-48.com (205.251.193.129), ns-385.awsdns-48.com (2600:9000:5301:8100::1), ns-777.awsdns-33.net (205.251.195.9), ns-777.awsdns-33.net (2600:9000:5303:900::1); 2026010601 on ns1.ning.com (208.82.16.96), ns2.ning.com (208.82.16.64). 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

Recent checks

!

Full report

Domain & DNS report for ning.com ›

Mail

fail

21 passed 5 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
  • !
    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: mx.ning.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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), k1 (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 ning.com ›