townnews.com

Checked 22 October 2026, 11:11 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 7 info

Registration

info

.com generic · Tucows Domains Inc. · expires 2027-03-07

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Tucows Domains Inc.
Registered
6 March 1996
Last changed
5 February 2026
Expires
7 March 2027
Status
active
Registry nameservers
bowen.ns.cloudflare.com, lindsey.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-03-07 #3
    The registration is valid until 2027-03-07 (135 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

bowen.ns.cloudflare.com, lindsey.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
bowen.ns.cloudflare.com, lindsey.ns.cloudflare.com
NS in the zone
bowen.ns.cloudflare.com, lindsey.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
bowen.ns.cloudflare.com172.64.35.83 162.159.44.83 108.162.195.83 2803:f800:50::6ca2:c353 2606:4700:58::a29f:2c53 2a06:98c1:50::ac40:2353AS13335 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.83 162.159.44.83 172.64.35.83 2606:4700:58::a29f:2c53 2803:f800:50::6ca2:c353 2a06:98c1:50::ac40:2353
lindsey.ns.cloudflare.com162.159.38.5 108.162.194.5 172.64.34.5 2606:4700:50::a29f:2605 2803:f800:50::6ca2:c205 2a06:98c1:50::ac40:2205AS13335 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.194.5 162.159.38.5 172.64.34.5 2606:4700:50::a29f:2605 2803:f800:50::6ca2:c205 2a06:98c1:50::ac40:2205

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: bowen.ns.cloudflare.com, lindsey.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
bowen.ns.cloudflare.com 172.64.35.83NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
bowen.ns.cloudflare.com 162.159.44.83NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
bowen.ns.cloudflare.com 108.162.195.83NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
bowen.ns.cloudflare.com 2803:f800:50::6ca2:c353NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
bowen.ns.cloudflare.com 2606:4700:58::a29f:2c53NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
bowen.ns.cloudflare.com 2a06:98c1:50::ac40:2353NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
lindsey.ns.cloudflare.com 162.159.38.5NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
lindsey.ns.cloudflare.com 108.162.194.5NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
lindsey.ns.cloudflare.com 172.64.34.5NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
lindsey.ns.cloudflare.com 2606:4700:50::a29f:2605NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
lindsey.ns.cloudflare.com 2803:f800:50::6ca2:c205NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
lindsey.ns.cloudflare.com 2a06:98c1:50::ac40:2205NOERROR, 5 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: bowen.ns.cloudflare.com: "2026.10.2"; lindsey.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 2415891002 · primary bowen.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
bowen.ns.cloudflare.com (172.64.35.83)2415891002
bowen.ns.cloudflare.com (162.159.44.83)2415891002
bowen.ns.cloudflare.com (108.162.195.83)2415891002
bowen.ns.cloudflare.com (2803:f800:50::6ca2:c353)2415891002
bowen.ns.cloudflare.com (2606:4700:58::a29f:2c53)2415891002
bowen.ns.cloudflare.com (2a06:98c1:50::ac40:2353)2415891002
lindsey.ns.cloudflare.com (162.159.38.5)2415891002
lindsey.ns.cloudflare.com (108.162.194.5)2415891002
lindsey.ns.cloudflare.com (172.64.34.5)2415891002
lindsey.ns.cloudflare.com (2606:4700:50::a29f:2605)2415891002
lindsey.ns.cloudflare.com (2803:f800:50::6ca2:c205)2415891002
lindsey.ns.cloudflare.com (2a06:98c1:50::ac40:2205)2415891002

Checks

  • ✓ Serial 2415891002 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 bowen.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 2415891002 is a Unix timestamp (2046-07-22 16:50 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

info

18 records at the apex

Found

Read from
172.64.35.83:53
TypeValueTTL
SOAbowen.ns.cloudflare.com. dns.cloudflare.com. 2415891002 10000 2400 604800 18001800
NSbowen.ns.cloudflare.com.86400
NSlindsey.ns.cloudflare.com.86400
A192.104.182.1097200
A192.104.182.2097200
MX10 mx0b-00292f01.pphosted.com.300
MX20 mx0a-00292f01.pphosted.com.300
TXT"202608261322270ckn8zdya1r8vzr5gat7own7embisnti5vv2qwid5gdkxbj5c2"300
TXT"MS=ms99388473"300
TXT"ZOOM_verify_7WOzFa0DQOeJ96Lz-SYEnQ"300
TXT"adobe-idp-site-verification=039adc5854d3e2024125d174b988acafb7b42ea4a6c3fcc348d938dbd0b7f7ff"300
TXT"atlassian-domain-verification=fBRvMLM2ATaVmzCi57T9yMSETTC0a3xPYGHaf71iBaLnzKR/i/UmQjS9orOa1bxa"300
TXT"canva-site-verification=JFLx_L80gxz-FAoD1FTRiA"300
TXT"google-site-verification=T6HJuv9f95xxWtqSNpW3VV9QEgo_kJmGaNkcDFNN40g"300
TXT"google-site-verification=w5BFcSW3vwENam3mDcsNy3KuZyfbP13xLNi1tbWgEFk"300
TXT"knowbe4-site-verification=4d74bbd68c11b993425e4dcc4cf20593"300
TXT"segment-site-verification=3yOFMQ0IbD6rsGmfonOEtZm2gf4FAVxH"300
TXT"v=spf1 mx include:tn-cloud.net ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 2h, MX 5m, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; 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
  • 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