newswire.com

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

Registration

info

.com generic · GoDaddy.com, LLC · expires 2031-01-21

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
20 January 1995
Last changed
7 February 2023
Expires
21 January 2031
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
betty.ns.cloudflare.com, stan.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 2031-01-21 #3
    The registration is valid until 2031-01-21 (1551 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

betty.ns.cloudflare.com, stan.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
betty.ns.cloudflare.com, stan.ns.cloudflare.com
NS in the zone
betty.ns.cloudflare.com, stan.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
betty.ns.cloudflare.com108.162.192.75 172.64.32.75 173.245.58.75 2803:f800:50::6ca2:c04b 2606:4700:50::adf5:3a4b 2a06:98c1:50::ac40:204bAS13335 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.75 172.64.32.75 173.245.58.75 2606:4700:50::adf5:3a4b 2803:f800:50::6ca2:c04b 2a06:98c1:50::ac40:204b
stan.ns.cloudflare.com108.162.193.235 173.245.59.235 172.64.33.235 2803:f800:50::6ca2:c1eb 2a06:98c1:50::ac40:21eb 2606:4700:58::adf5:3bebAS13335 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.193.235 172.64.33.235 173.245.59.235 2606:4700:58::adf5:3beb 2803:f800:50::6ca2:c1eb 2a06:98c1:50::ac40:21eb

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: betty.ns.cloudflare.com, stan.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
betty.ns.cloudflare.com 108.162.192.75NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
betty.ns.cloudflare.com 172.64.32.75NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
betty.ns.cloudflare.com 173.245.58.75NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
betty.ns.cloudflare.com 2803:f800:50::6ca2:c04bNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
betty.ns.cloudflare.com 2606:4700:50::adf5:3a4bNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
betty.ns.cloudflare.com 2a06:98c1:50::ac40:204bNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
stan.ns.cloudflare.com 108.162.193.235NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
stan.ns.cloudflare.com 173.245.59.235NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
stan.ns.cloudflare.com 172.64.33.235NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
stan.ns.cloudflare.com 2803:f800:50::6ca2:c1ebNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
stan.ns.cloudflare.com 2a06:98c1:50::ac40:21ebNOERROR, 19 ms, authoritativenoyes / yesrefused2026.10.2
stan.ns.cloudflare.com 2606:4700:58::adf5:3bebNOERROR, 15 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: betty.ns.cloudflare.com: "2026.10.2"; stan.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 2418077206 · primary betty.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
betty.ns.cloudflare.com (108.162.192.75)2418077206
betty.ns.cloudflare.com (172.64.32.75)2418077206
betty.ns.cloudflare.com (173.245.58.75)2418077206
betty.ns.cloudflare.com (2803:f800:50::6ca2:c04b)2418077206
betty.ns.cloudflare.com (2606:4700:50::adf5:3a4b)2418077206
betty.ns.cloudflare.com (2a06:98c1:50::ac40:204b)2418077206
stan.ns.cloudflare.com (108.162.193.235)2418077206
stan.ns.cloudflare.com (173.245.59.235)2418077206
stan.ns.cloudflare.com (172.64.33.235)2418077206
stan.ns.cloudflare.com (2803:f800:50::6ca2:c1eb)2418077206
stan.ns.cloudflare.com (2a06:98c1:50::ac40:21eb)2418077206
stan.ns.cloudflare.com (2606:4700:58::adf5:3beb)2418077206

Checks

  • ✓ Serial 2418077206 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 betty.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 2418077206 is a Unix timestamp (2046-08-17 00:06 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

21 records at the apex

Found

Read from
108.162.192.75:53
TypeValueTTL
SOAbetty.ns.cloudflare.com. dns.cloudflare.com. 2418077206 10000 2400 604800 18001800
NSbetty.ns.cloudflare.com.86400
NSstan.ns.cloudflare.com.86400
A34.70.61.30120
A34.66.165.10120
A34.133.122.11120
A35.238.119.212120
A35.232.213.243120
A34.71.54.51120
MX0 newswire-com.mail.protection.outlook.com.3600
TXT"MS=ms76894685"60
TXT"abuseipdb-verification=CHvZqjrN"60
TXT"adobe-idp-site-verification=37f509df1fdb67325d90fdb8d426a7042e45133985fa7d973baf549381a750c5"60
TXT"facebook-domain-verification=mzs1mtdgfhri6juvb7s200ywbfniyx"60
TXT"google-site-verification=-JZeDOzHLJr882harp14fYT8QCvi5GDP1x1bHFCBF-U"60
TXT"google-site-verification=1WpIbfr1E-YoYK_E-2zyWsfYYfmAicTGO5g_fQEOW9Y"60
TXT"google-site-verification=4HaVceNWgurTJbU9PgSnFWFLcurOLxBZkPU46MBrkkw"60
TXT"google-site-verification=_s7OfqZB1z1UQRqXZeE6U5yY0miEJyt2MYc5NK1Boco"60
TXT"google-site-verification=pbPBwdwvvZz024wNGYD_4Lzdy1IdLWqPZDTPZMNyCfI"60
TXT"google-site-verification=rysuJcfWrCys6xcsn522Cn-40oYbQwqemxl6HTx_j5Q"60
TXT"v=spf1 include:spf.protection.outlook.com include:21179411.spf08.hubspotemail.net include:mktomail.com include:_spf.salesforce.com ~all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m). 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.
  • 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