`troubleshooting-google.com`

DNSSEC	⚠️ Not signed
A	206.71.149.193^{🇬🇧 BLNWX206.71.149.0/24 BL Networks}
NS	`molly.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3acd^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`molly.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0cd^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`molly.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20cd^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`molly.ns.cloudflare.com`
		A	108.162.192.205^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`molly.ns.cloudflare.com`
		A	172.64.32.205^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`molly.ns.cloudflare.com`
		A	173.245.58.205^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`molly.ns.cloudflare.com`
NS	`yadiel.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c04^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yadiel.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c304^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`yadiel.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2304^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`yadiel.ns.cloudflare.com`
		A	108.162.195.4^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yadiel.ns.cloudflare.com`
		A	162.159.44.4^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yadiel.ns.cloudflare.com`
		A	172.64.35.4^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yadiel.ns.cloudflare.com`
SOA	`molly.ns.cloudflare.com`dns@cloudflare.com serial=2412089994

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1786616559

Same first word

troubleshooting-google.com

DNS History

10 records (3 active, 7 former)

○NSdns1.name-services.com2015-08-01 → 2016-07-16 · 4 obs

● 2015-08-01 19:17:38
● 2016-07-16 16:09:22
○ 2017-03-26 04:37:44
○ 2026-08-13 10:42:52

○NSdns2.name-services.com2015-08-01 → 2016-07-16 · 4 obs

● 2015-08-01 19:17:38
● 2016-07-16 16:09:22
○ 2017-03-26 04:37:44
○ 2026-08-13 10:42:52

○NSdns3.name-services.com2015-08-01 → 2016-07-16 · 4 obs

● 2015-08-01 19:17:38
● 2016-07-16 16:09:22
○ 2017-03-26 04:37:44
○ 2026-08-13 10:42:52

○NSdns4.name-services.com2015-08-01 → 2016-07-16 · 4 obs

● 2015-08-01 19:17:38
● 2016-07-16 16:09:22
○ 2017-03-26 04:37:44
○ 2026-08-13 10:42:52

○NSdns5.name-services.com2015-08-01 → 2016-07-16 · 4 obs

● 2015-08-01 19:17:38
● 2016-07-16 16:09:22
○ 2017-03-26 04:37:44
○ 2026-08-13 10:42:52

●NSmolly.ns.cloudflare.com2026-08-13 → 2026-08-13 · 3 obs

○ 2017-03-26 04:37:44
● 2026-08-13 02:54:10
● 2026-08-13 10:42:52

●NSyadiel.ns.cloudflare.com2026-08-13 → 2026-08-13 · 3 obs

○ 2017-03-26 04:37:44
● 2026-08-13 02:54:10
● 2026-08-13 10:42:52

○MXp.nsm.ctmail.com2015-08-01 → 2016-03-14 · 4 obs

● 2015-08-01 19:17:38
● 2016-03-14 14:57:10
○ 2016-07-16 16:09:22
○ 2026-08-13 10:42:52

●A206.71.149.1932026-08-13 → 2026-08-13 · 3 obs

○ 2017-03-26 04:37:44
● 2026-08-13 02:54:10
● 2026-08-13 10:42:52

○A8.5.1.402015-08-01 → 2016-07-16 · 4 obs

● 2015-08-01 19:17:38
● 2016-07-16 16:09:22
○ 2017-03-26 04:37:44
○ 2026-08-13 10:42:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
troubleshooting-google.com	molly.ns.cloudflare.com, yadiel.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.4

NS records: molly.ns.cloudflare.com, yadiel.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for troubleshooting-google.com (unsigned zone)

⏱️ Timing

Total: 133ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`206.71.149.193`
NS	2	`molly.ns.cloudflare.com, yadiel.ns.cloudflare.com`
SOA	1	`molly.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (molly.ns.cloudflare.com, molly.ns.cloudflare.com, molly.ns.cloudflare.com...)

Analysis

IP Addresses

troubleshooting-google.com has exactly one IP address — 206.71.149.193.

systemrecovery-gmail.com, recoverysystem-gmail.com, verify-binance.us plus two other host names have IP numbers in common with troubleshooting-google.com.

Name Servers

troubleshooting-google.com is delegated to two name servers: molly.ns.cloudflare.com and yadiel.ns.cloudflare.com.

The name server configuration of troubleshooting-google.com is shared with other domains, for instance native-coinbase.com, fidelityishdow.com, control-gemini.com and two others.

There is at least partial name server overlap between troubleshooting-google.com and other domains — new77-rest.vip, sxwlgg.com, platinumarenazone.com and two more among them.

These name servers frequently co-occur with the name servers ariadne.ns.cloudflare.com and roman.ns.cloudflare.com.

Hosts with 6 IP addresses each:

molly.ns.cloudflare.com resolves to 108.162.192.205, 172.64.32.205, 173.245.58.205 and 3 other IP addresses.

yadiel.ns.cloudflare.com resolves to 108.162.195.4, 162.159.44.4, 172.64.35.4 and 3 other IP addresses.

troubleshooting-google.com - robtex.com