🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`node-cloud.net`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::ac43:d315^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3035::6815:177c^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.23.124^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.211.21^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`lily.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a82^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lily.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c082^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lily.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2082^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lily.ns.cloudflare.com`
		A	108.162.192.130^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lily.ns.cloudflare.com`
		A	172.64.32.130^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lily.ns.cloudflare.com`
		A	173.245.58.130^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lily.ns.cloudflare.com`
NS	`yahir.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c22^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yahir.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c322^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`yahir.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2322^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`yahir.ns.cloudflare.com`
		A	108.162.195.34^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yahir.ns.cloudflare.com`
		A	162.159.44.34^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yahir.ns.cloudflare.com`
		A	172.64.35.34^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`yahir.ns.cloudflare.com`
MX	`mx2.zoho.jp` ⭐
		A	193.118.161.144^{🇯🇵 ZJC-AS-AP193.118.161.0/24 COLT ASIA Telecom}
			PTR	`mx2.zoho.jp`
			PTR	`mx3.zoho.jp`
			PTR	`mx.zoho.jp`
MX	`mx3.zoho.jp`⁽²⁰⁾
		A	103.163.152.144^{🇯🇵 ZJC-AS-AP103.163.152.0/24 Zoho Japan Corporation Minato-Mirai-Center Bldg. 13F, 3-6-1 Nishi-ku,}
			PTR	`mx2.zoho.jp`
			PTR	`mx3.zoho.jp`
			PTR	`mx.zoho.jp`
MX	`mx.zoho.jp`⁽⁵⁰⁾
		A	103.163.152.144^{🇯🇵 ZJC-AS-AP103.163.152.0/24 Zoho Japan Corporation Minato-Mirai-Center Bldg. 13F, 3-6-1 Nishi-ku,}
			PTR	`mx2.zoho.jp`
			PTR	`mx3.zoho.jp`
			PTR	`mx.zoho.jp`
		A	193.118.161.144^{🇯🇵 ZJC-AS-AP193.118.161.0/24 COLT ASIA Telecom}
			PTR	`mx2.zoho.jp`
			PTR	`mx3.zoho.jp`
			PTR	`mx.zoho.jp`
TXT	`google-site-verification=N2iwJmEgEfipHfEqZt8dNoj9YdZxo4jyGnFFh6TvMMc`
TXT	`v=spf1 include:zohomail.jp ~all`
TXT	`zoho-verification=zb69586002.zmverify.zoho.jp`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.23.124, 172.67.211.21
		IPv6 hints	2606:4700:3030::ac43:d315, 2606:4700:3035::6815:177c
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=178, name=cloudflare-ech.com
SOA	`lily.ns.cloudflare.com`dns@cloudflare.com serial=2413325647

`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=1788351155

Same first word

node-cloud.cc

node-cloud.net

Similar names

cloud-node.ru

cloud-node.de

cloud-node.net

cloud-node.digital

cloud-oden.duckdns.org

cloud-node.dk

cloud-node.com

cloud-node.uk

Previous names

Next names

DNS History

9 records (9 active, 0 former)

●NSlily.ns.cloudflare.com2026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

●NSyahir.ns.cloudflare.com2026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

●MXmx.zoho.jp2026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

●MXmx2.zoho.jp2026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

●MXmx3.zoho.jp2026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

●A104.21.23.1242026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

●A172.67.211.212026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

●A2606:4700:3030::ac43:d3152026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

●A2606:4700:3035::6815:177c2026-09-01 → 2026-09-02 · 2 obs

● 2026-09-01 04:09:28
● 2026-09-02 12:25:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	g.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net...	-
node-cloud.net	lily.ns.cloudflare.com, yahir.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.35.34

NS records: lily.ns.cloudflare.com, yahir.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for node-cloud.net (unsigned zone)

⏱️ Timing

Total: 1254ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.23.124, 172.67.211.21`
AAAA	2	`2606:4700:3030::ac43:d315, 2606:4700:3035::6815:177c`
NS	2	`lily.ns.cloudflare.com, yahir.ns.cloudflare.com`
MX	3	`mx.zoho.jp (pri: 10), mx2.zoho.jp (pri: 20)...`
TXT	3	`google-site-verification=N2iwJmEgEfipHfE, v=spf1 include:zohomail.jp ~all...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`lily.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

node-cloud.net directs to four IP numbers, which are 104.21.23.124, 172.67.211.21, 2606:4700:3030::ac43:d315 and 2606:4700:3035::6815:177c.

Two other host names, along with barbarajimenez.com.mx, ctkcps.com and pcagmz.cards, also share IP numbers with node-cloud.net.

Name Servers

Two name servers handle the delegation for node-cloud.net: lily.ns.cloudflare.com and yahir.ns.cloudflare.com.

node-cloud.net shares its NS records with other domains, for example aliroosta11111.workers.dev, sheetalgyan.in, x75ggwtwvn.workers.dev and two others.

The name servers of node-cloud.net overlap at least partially with those of other domains — among them activedirectory.com.cn, hywaterbottle.it.com, callcove.app and two more.

These name servers commonly appear in combination with the name servers ian.ns.cloudflare.com.

DNS names with 6 IP addresses:

lily.ns.cloudflare.com resolves to 108.162.192.130, 172.64.32.130 and 173.245.58.130 among others, with 3 other IP addresses in total.

yahir.ns.cloudflare.com resolves to 108.162.195.34, 162.159.44.34 and 172.64.35.34 among others, with 3 other IP addresses in total.

Mail Servers

Mail for node-cloud.net is routed through three mail servers — mx2.zoho.jp, mx3.zoho.jp and mx.zoho.jp.

There is at least a partial MX overlap between node-cloud.net and other domains, including forum-lucifer.com, sailboatui.com, tkslab.com and two others.

Host names that have two IP addresses:

mx.zoho.jp resolves to two addresses: 103.163.152.144 and 193.118.161.144.

Host names that point to one IP address:

The hostname mx2.zoho.jp resolves to 193.118.161.144.

The hostname mx3.zoho.jp resolves to 103.163.152.144.

mx.zoho.jp along with mx3.zoho.jp each resolve to 103.163.152.144 IP addresses.

mx.zoho.jp along with mx2.zoho.jp each resolve to 193.118.161.144 IP addresses.

node-cloud.net - robtex.com

node-cloud.net

net

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`node-cloud.net`

`net`