ning.com

Checked 22 October 2026, 10:03 UTC · via 8.8.8.8
!Passed with warnings
25 passed 3 warnings 0 failed 3 info

Registration

info

.com generic · Key-Systems GmbH · expires 2026-12-16

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Key-Systems GmbH
Registered
16 December 2003
Last changed
29 November 2025
Expires
16 December 2026
Status
client transfer prohibited
Registry nameservers
ns-1132.awsdns-13.org, ns-1707.awsdns-21.co.uk, ns-385.awsdns-48.com, ns-777.awsdns-33.net, ns1.ning.com, ns2.ning.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2026-12-16 #3
    The registration is valid until 2026-12-16 (55 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns-1132.awsdns-13.org, ns-1707.awsdns-21.co.uk, ns-385.awsdns-48.com, ns-777.awsdns-33.net, ns1.ning.com, ns2.ning.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns-1132.awsdns-13.org, ns-1707.awsdns-21.co.uk, ns-385.awsdns-48.com, ns-777.awsdns-33.net, ns1.ning.com, ns2.ning.com
NS in the zone
ns-1132.awsdns-13.org, ns-1707.awsdns-21.co.uk, ns-385.awsdns-48.com, ns-777.awsdns-33.net, ns1.ning.com, ns2.ning.com
NameserverAddressesNetwork (AS)Glue
ns-1132.awsdns-13.org205.251.196.108 2600:9000:5304:6c00::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns-1707.awsdns-21.co.uk205.251.198.171 2600:9000:5306:ab00::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns-385.awsdns-48.com205.251.193.129 2600:9000:5301:8100::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US205.251.193.129 2600:9000:5301:8100::1
ns-777.awsdns-33.net205.251.195.9 2600:9000:5303:900::1AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns1.ning.com208.82.16.96AS13535 NING - Ning Interactive, Inc., US208.82.16.96
ns2.ning.com208.82.16.64AS13535 NING - Ning Interactive, Inc., US208.82.16.64

Checks

  • ✓ 6 nameservers #6
    Delegated to ns-1132.awsdns-13.org, ns-1707.awsdns-21.co.uk, ns-385.awsdns-48.com, ns-777.awsdns-33.net, ns1.ning.com, ns2.ning.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.ning.com, ns2.ning.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 5 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS13535 (NING - Ning Interactive, Inc., US): 2 addresses; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 8 addresses.
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .net, .org, .uk.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.ning.com, ns2.ning.com.
    #13

Nameservers

warn

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-1132.awsdns-13.org 205.251.196.108NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns-1132.awsdns-13.org 2600:9000:5304:6c00::1NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns-1707.awsdns-21.co.uk 205.251.198.171NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns-1707.awsdns-21.co.uk 2600:9000:5306:ab00::1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns-385.awsdns-48.com 205.251.193.129NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns-385.awsdns-48.com 2600:9000:5301:8100::1NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns-777.awsdns-33.net 205.251.195.9NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns-777.awsdns-33.net 2600:9000:5303:900::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.ning.com 208.82.16.96NOERROR, 119 ms, authoritativenoyes / yesrefused9.10.3-P4-Ubuntu
ns2.ning.com 208.82.16.64NOERROR, 116 ms, authoritativenoyes / yesrefused9.10.3-P4-Ubuntu

Checks

  • ✓ All respond #14
    All 10 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    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
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2 · primary ns-385.awsdns-48.com

Found

Primary (MNAME)
ns-385.awsdns-48.com
Contact (RNAME)
awsdns-hostmaster.amazon.com
Serial
2
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns-1132.awsdns-13.org (205.251.196.108)2
ns-1132.awsdns-13.org (2600:9000:5304:6c00::1)2
ns-1707.awsdns-21.co.uk (205.251.198.171)2
ns-1707.awsdns-21.co.uk (2600:9000:5306:ab00::1)2
ns-385.awsdns-48.com (205.251.193.129)2
ns-385.awsdns-48.com (2600:9000:5301:8100::1)2
ns-777.awsdns-33.net (205.251.195.9)2
ns-777.awsdns-33.net (2600:9000:5303:900::1)2
ns1.ning.com (208.82.16.96)2026010601
ns2.ning.com (208.82.16.64)2026010601

Checks

  • !
    Serials differ
    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
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns-385.awsdns-48.com is one of the listed nameservers.
  • ✓ Contact awsdns-hostmaster@amazon.com #25
    The SOA RNAME awsdns-hostmaster.amazon.com means awsdns-hostmaster@amazon.com.
  • ✓ Counter serial #26
    The serial 2 is a plain counter.

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

info

15 records at the apex

Found

Read from
205.251.196.108:53
TypeValueTTL
SOAns-385.awsdns-48.com. awsdns-hostmaster.amazon.com. 2 7200 900 1209600 86400900
NSns-1132.awsdns-13.org.3600
NSns-1707.awsdns-21.co.uk.3600
NSns-385.awsdns-48.com.3600
NSns-777.awsdns-33.net.3600
NSns1.ning.com.3600
NSns2.ning.com.3600
A208.82.16.81300
MX10 mx.ning.com.360
TXT"esputnik-verification=RVNQX0RWS19WMQAA95gAAAFyVhp3z-ieBFhqSOEX"300
TXT"google-site-verification=ku8w5VPI-afHuvdrrjowlx51LUumyGe-l9vApRORIRQ"300
TXT"v=spf1 include:spf2.esputnik.com include:servers.mcsv.net include:mail.zendesk.com ip4:208.82.16.0/22 ip4:8.6.19.94 a mx ~all"300
CAA0 iodef "mailto:abuse@ning.com"300
CAA0 issue "letsencrypt.org"300
CAA0 issue "sectigo.com"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 6m, NS 1h. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, sectigo.com.