🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`rootcomputing.net`

DNSSEC	⚠️ Not signed
A	2604:a880:400:d1:0:4:bb2b:8001^{🇺🇸 DIGITALOCEAN2604:a880:400::/48 DigitalOcean}
A	161.35.111.69^{🇺🇸 DIGITALOCEAN161.35.96.0/20 DigitalOcean}
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com`
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
SOA	`ns1.digitalocean.com`hostmaster@rootcomputing.net serial=0

`net`

	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=1794496656

Same first word

rootcomputing.com

rootcomputing.co

rootcomputing.net

Previous names

Next names

DNS History

17 records (5 active, 12 former)

○NSns-cloud-e1.googledomains.com2016-06-18 → 2017-02-13 · 5 obs

○ 2016-02-03 03:13:28
● 2016-06-18 16:36:46
● 2017-02-13 04:13:52
○ 2019-03-15 14:40:22
○ 2026-11-12 15:25:28

○NSns-cloud-e2.googledomains.com2016-06-18 → 2017-02-13 · 5 obs

○ 2016-02-03 03:13:28
● 2016-06-18 16:36:46
● 2017-02-13 04:13:52
○ 2019-03-15 14:40:22
○ 2026-11-12 15:25:28

○NSns-cloud-e3.googledomains.com2016-06-18 → 2017-02-13 · 5 obs

○ 2016-02-03 03:13:28
● 2016-06-18 16:36:46
● 2017-02-13 04:13:52
○ 2019-03-15 14:40:22
○ 2026-11-12 15:25:28

○NSns-cloud-e4.googledomains.com2016-06-18 → 2017-02-13 · 5 obs

○ 2016-02-03 03:13:28
● 2016-06-18 16:36:46
● 2017-02-13 04:13:52
○ 2019-03-15 14:40:22
○ 2026-11-12 15:25:28

●NSns1.digitalocean.com2016-02-03 → 2026-11-12 · 6 obs

○ 2015-11-10 01:19:44
● 2016-02-03 03:13:28
○ 2016-06-18 16:36:46
○ 2017-02-13 04:13:52
● 2019-03-15 14:40:22
● 2026-11-12 15:25:28

●NSns2.digitalocean.com2016-02-03 → 2026-11-12 · 6 obs

○ 2015-11-10 01:19:44
● 2016-02-03 03:13:28
○ 2016-06-18 16:36:46
○ 2017-02-13 04:13:52
● 2019-03-15 14:40:22
● 2026-11-12 15:25:28

●NSns3.digitalocean.com2016-02-03 → 2026-11-12 · 6 obs

○ 2015-11-10 01:19:44
● 2016-02-03 03:13:28
○ 2016-06-18 16:36:46
○ 2017-02-13 04:13:52
● 2019-03-15 14:40:22
● 2026-11-12 15:25:28

○NSns51.1and1.com2015-07-03 → 2015-11-10 · 4 obs

● 2015-07-03 20:32:10
● 2015-11-10 01:19:44
○ 2016-02-03 03:13:28
○ 2026-11-12 15:25:28

○NSns52.1and1.com2015-07-03 → 2015-11-10 · 4 obs

● 2015-07-03 20:32:10
● 2015-11-10 01:19:44
○ 2016-02-03 03:13:28
○ 2026-11-12 15:25:28

○MXmx00.1and1.com2015-07-03 → 2015-11-10 · 4 obs

● 2015-07-03 20:32:10
● 2015-11-10 01:19:44
○ 2016-02-03 03:13:28
○ 2026-11-12 15:25:28

○MXmx01.1and1.com2015-07-03 → 2015-11-10 · 4 obs

● 2015-07-03 20:32:10
● 2015-11-10 01:19:44
○ 2016-02-03 03:13:28
○ 2026-11-12 15:25:28

○A104.236.78.832016-02-03 → 2017-02-13 · 5 obs

○ 2015-11-10 01:19:44
● 2016-02-03 03:13:28
● 2017-02-13 04:13:52
○ 2019-03-15 14:40:22
○ 2026-11-12 15:25:28

●A161.35.111.692026-08-26 → 2026-11-12 · 3 obs

○ 2019-03-15 14:40:22
● 2026-08-26 07:23:32
● 2026-11-12 15:25:28

○A198.71.53.1022015-07-03 → 2015-11-10 · 4 obs

● 2015-07-03 20:32:10
● 2015-11-10 01:19:44
○ 2016-02-03 03:13:28
○ 2026-11-12 15:25:28

●A2604:a880:400:d1:0:4:bb2b:80012026-08-26 → 2026-11-12 · 3 obs

○ 2019-03-15 14:40:22
● 2026-08-26 07:23:32
● 2026-11-12 15:25:28

○A2607:f1c0:1000:6013:f179:218:687a:c0102015-07-03 → 2015-11-10 · 4 obs

● 2015-07-03 20:32:10
● 2015-11-10 01:19:44
○ 2016-02-03 03:13:28
○ 2026-11-12 15:25:28

○A67.205.190.832019-03-15 → 2019-03-15 · 4 obs

○ 2017-02-13 04:13:52
● 2019-03-15 14:40:22
○ 2026-08-26 07:23:32
○ 2026-11-12 15:25:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	c.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net, b.gtld-servers.net...	-
rootcomputing.net	ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com	-

✅ Authoritative Response

Server:172.64.52.210

NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for rootcomputing.net (unsigned zone)

⏱️ Timing

Total: 466ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`161.35.111.69`
AAAA	1	`2604:a880:400:d1:0:4:bb2b:8001`
NS	3	`ns2.digitalocean.com, ns3.digitalocean.com...`
SOA	1	`ns1.digitalocean.com hostmaster.rootcomp`

Analysis

IP Addresses

rootcomputing.net directs to two IP numbers, 161.35.111.69 and 2604:a880:400:d1:0:4:bb2b:8001

Other host names, such as webcookie.net, share IP numbers with rootcomputing.net.

Name Servers

rootcomputing.net is delegated to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

rootcomputing.net shares at least some of its name servers with other domains, including vijayalakshmiimpex.com, kompetoo.com, 1.0.0.6.8.d.8.1.0.0.0.0.0.0.0.0.0.d.0.0.3.0.0.0.0.c.0.b.3.0.a.2.ip6.arpa and two others.

ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com each resolve to two IP addresses: ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com resolves to 172.64.49.209 and 2606:4700:52::ac40:31d1.

rootcomputing.net - robtex.com