wellandgood.com

Checked 22 October 2026, 11:30 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 5 info

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-06-11

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
11 June 2001
Last changed
30 October 2025
Expires
11 June 2027
Status
client transfer prohibited
Registry nameservers
houston.ns.cloudflare.com, lily.ns.cloudflare.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 2027-06-11 #3
    The registration is valid until 2027-06-11 (231 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

houston.ns.cloudflare.com, lily.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
houston.ns.cloudflare.com, lily.ns.cloudflare.com
NS in the zone
houston.ns.cloudflare.com, lily.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
houston.ns.cloudflare.com172.64.35.52 162.159.44.52 108.162.195.52 2a06:98c1:50::ac40:2334 2606:4700:58::a29f:2c34 2803:f800:50::6ca2:c334AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.195.52 162.159.44.52 172.64.35.52 2606:4700:58::a29f:2c34 2803:f800:50::6ca2:c334 2a06:98c1:50::ac40:2334
lily.ns.cloudflare.com108.162.192.130 173.245.58.130 172.64.32.130 2803:f800:50::6ca2:c082 2606:4700:50::adf5:3a82 2a06:98c1:50::ac40:2082AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.192.130 172.64.32.130 173.245.58.130 2606:4700:50::adf5:3a82 2803:f800:50::6ca2:c082 2a06:98c1:50::ac40:2082

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: houston.ns.cloudflare.com, lily.ns.cloudflare.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ 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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
houston.ns.cloudflare.com 172.64.35.52NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
houston.ns.cloudflare.com 162.159.44.52NOERROR, 33 ms, authoritativenoyes / yesrefused2026.10.2
houston.ns.cloudflare.com 108.162.195.52NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
houston.ns.cloudflare.com 2a06:98c1:50::ac40:2334NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
houston.ns.cloudflare.com 2606:4700:58::a29f:2c34NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
houston.ns.cloudflare.com 2803:f800:50::6ca2:c334NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
lily.ns.cloudflare.com 108.162.192.130NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
lily.ns.cloudflare.com 173.245.58.130NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
lily.ns.cloudflare.com 172.64.32.130NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
lily.ns.cloudflare.com 2803:f800:50::6ca2:c082NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
lily.ns.cloudflare.com 2606:4700:50::adf5:3a82NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
lily.ns.cloudflare.com 2a06:98c1:50::ac40:2082NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: houston.ns.cloudflare.com: "2026.10.2"; lily.ns.cloudflare.com: "2026.10.2". 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

pass

serial 2418038048 · primary houston.ns.cloudflare.com

Found

Primary (MNAME)
houston.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2418038048
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
houston.ns.cloudflare.com (172.64.35.52)2418038048
houston.ns.cloudflare.com (162.159.44.52)2418038048
houston.ns.cloudflare.com (108.162.195.52)2418038048
houston.ns.cloudflare.com (2a06:98c1:50::ac40:2334)2418038048
houston.ns.cloudflare.com (2606:4700:58::a29f:2c34)2418038048
houston.ns.cloudflare.com (2803:f800:50::6ca2:c334)2418038048
lily.ns.cloudflare.com (108.162.192.130)2418038048
lily.ns.cloudflare.com (173.245.58.130)2418038048
lily.ns.cloudflare.com (172.64.32.130)2418038048
lily.ns.cloudflare.com (2803:f800:50::6ca2:c082)2418038048
lily.ns.cloudflare.com (2606:4700:50::adf5:3a82)2418038048
lily.ns.cloudflare.com (2a06:98c1:50::ac40:2082)2418038048

Checks

  • ✓ Serial 2418038048 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver houston.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2418038048 is a Unix timestamp (2046-08-16 13:14 UTC).

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

warn

20 records at the apex

Found

Read from
172.64.35.52:53
TypeValueTTL
SOAhouston.ns.cloudflare.com. dns.cloudflare.com. 2418038048 10000 2400 604800 18001800
NShouston.ns.cloudflare.com.86400
NSlily.ns.cloudflare.com.86400
A172.64.151.246300
A104.18.36.10300
AAAA2606:4700:4407::ac40:97f6300
AAAA2606:4700:440a::6812:240a300
MX1 ASPMX.L.GOOGLE.com.100
MX10 ASPMX2.GOOGLEMAIL.com.100
MX10 ASPMX3.GOOGLEMAIL.com.100
MX5 ALT1.ASPMX.L.GOOGLE.com.100
MX5 ALT2.ASPMX.L.GOOGLE.com.100
TXT"airtable-verification=05b23cb2d74b59bcedbe8683a15d4374"100
TXT"docusign=abc65147-8bac-4af7-a680-790ab69086d6"100
TXT"facebook-domain-verification=mywjdefscu9rpnn2xsob8i9kbn01vr"100
TXT"google-site-verification=2NU2Dc1xL6SQ9SGkorbAKVsCJ8WUzqJ3bHLPA1HI33Q"100
TXT"google-site-verification=N-FfNMvogAPK5rvEbz4_dK9ytfWyBqhz0Js3vrZkZTo"100
TXT"google-site-verification=kwnPh4P8y37YjvlRfMVYkDGFS82UC0rIMXYrjwN93Hs"100
TXT"google-site-verification=rL4Bvzm7zqU8BqNnXtlV9WjdNzQdqX_F0MvDQrFMO2w"100
TXT"v=spf1 ip4:23.227.8.96/29 include:shops.shopify.com include:mail.zendesk.com include:_spf.google.com ~all"100

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m40s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35