🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`helicontechnology.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::ac43:842f^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::6815:c9c^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.12.156^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.132.47^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`fay.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a73^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fay.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c073^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`fay.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2073^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`fay.ns.cloudflare.com`
		A	108.162.192.115^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fay.ns.cloudflare.com`
		A	172.64.32.115^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fay.ns.cloudflare.com`
		A	173.245.58.115^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fay.ns.cloudflare.com`
NS	`sid.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b8f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sid.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c18f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`sid.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:218f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`sid.ns.cloudflare.com`
		A	108.162.193.143^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sid.ns.cloudflare.com`
		A	172.64.33.143^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sid.ns.cloudflare.com`
		A	173.245.59.143^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sid.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com include:email.freshdesk.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.12.156, 172.67.132.47
		IPv6 hints	2606:4700:3033::ac43:842f, 2606:4700:3037::6815:c9c
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=140, name=cloudflare-ech.com
SOA	`fay.ns.cloudflare.com`dns@cloudflare.com serial=2415260793

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

Same first word

helicontechnology.com

Previous names

Next names

DNS History

17 records (11 active, 6 former)

●NSfay.ns.cloudflare.com2015-08-28 → 2026-11-09 · 2 obs

● 2015-08-28 03:11:06
● 2026-11-09 01:21:52

●NSsid.ns.cloudflare.com2015-08-28 → 2026-11-09 · 2 obs

● 2015-08-28 03:11:06
● 2026-11-09 01:21:52

●MXalt1.aspmx.l.google.com2015-08-28 → 2026-11-09 · 2 obs

● 2015-08-28 03:11:06
● 2026-11-09 01:21:52

●MXalt2.aspmx.l.google.com2015-08-28 → 2026-11-09 · 2 obs

● 2015-08-28 03:11:06
● 2026-11-09 01:21:52

●MXaspmx.l.google.com2015-08-28 → 2026-11-09 · 2 obs

● 2015-08-28 03:11:06
● 2026-11-09 01:21:52

●MXaspmx2.googlemail.com2015-08-28 → 2026-11-09 · 2 obs

● 2015-08-28 03:11:06
● 2026-11-09 01:21:52

●MXaspmx3.googlemail.com2015-08-28 → 2026-11-09 · 2 obs

● 2015-08-28 03:11:06
● 2026-11-09 01:21:52

●A104.21.12.1562026-09-17 → 2026-11-09 · 3 obs

○ 2020-01-27 05:55:28
● 2026-09-17 20:05:24
● 2026-11-09 01:21:52

○A104.28.12.672015-08-28 → 2020-01-27 · 4 obs

● 2015-08-28 03:11:06
● 2020-01-27 05:55:28
○ 2026-09-17 20:05:24
○ 2026-11-09 01:21:52

○A104.28.13.672015-08-28 → 2020-01-27 · 4 obs

● 2015-08-28 03:11:06
● 2020-01-27 05:55:28
○ 2026-09-17 20:05:24
○ 2026-11-09 01:21:52

●A172.67.132.472026-09-17 → 2026-11-09 · 3 obs

○ 2020-01-27 05:55:28
● 2026-09-17 20:05:24
● 2026-11-09 01:21:52

○A2400:cb00:2048:1::681c:c432015-08-28 → 2017-02-08 · 4 obs

● 2015-08-28 03:11:06
● 2017-02-08 20:36:32
○ 2020-01-27 05:55:28
○ 2026-11-09 01:21:52

○A2400:cb00:2048:1::681c:d432015-08-28 → 2017-02-08 · 4 obs

● 2015-08-28 03:11:06
● 2017-02-08 20:36:32
○ 2020-01-27 05:55:28
○ 2026-11-09 01:21:52

○A2606:4700:3030::681c:c432020-01-27 → 2020-01-27 · 4 obs

○ 2017-02-08 20:36:32
● 2020-01-27 05:55:28
○ 2026-09-17 20:05:24
○ 2026-11-09 01:21:52

○A2606:4700:3033::681c:d432020-01-27 → 2020-01-27 · 4 obs

○ 2017-02-08 20:36:32
● 2020-01-27 05:55:28
○ 2026-09-17 20:05:24
○ 2026-11-09 01:21:52

●A2606:4700:3033::ac43:842f2026-09-17 → 2026-11-09 · 3 obs

○ 2020-01-27 05:55:28
● 2026-09-17 20:05:24
● 2026-11-09 01:21:52

●A2606:4700:3037::6815:c9c2026-09-17 → 2026-11-09 · 3 obs

○ 2020-01-27 05:55:28
● 2026-09-17 20:05:24
● 2026-11-09 01:21:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, a.gtld-servers.net, k.gtld-servers.net, h.gtld-servers.net...	-
helicontechnology.com	fay.ns.cloudflare.com, sid.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.143

NS records: fay.ns.cloudflare.com, sid.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for helicontechnology.com (unsigned zone)

⏱️ Timing

Total: 930ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.132.47, 104.21.12.156`
AAAA	2	`2606:4700:3033::ac43:842f, 2606:4700:3037::6815:c9c`
NS	2	`fay.ns.cloudflare.com, sid.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)...`
TXT	1	`v=spf1 include:_spf.google.com include:e`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`fay.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

helicontechnology.com directs to four IP numbers, which are 104.21.12.156, 172.67.132.47, 2606:4700:3033::ac43:842f and 2606:4700:3037::6815:c9c.

Additional host names — javx14.top, vibrant-reed.com, chenriang.me and two others — share IP numbers with helicontechnology.com.

Name Servers

helicontechnology.com uses two name servers for its delegation: fay.ns.cloudflare.com and sid.ns.cloudflare.com.

helicontechnology.com shares its name server setup with other domains, including wingmen.security, edmundfitzgerald.app, pioneer-networks.com and two others.

At least some of helicontechnology.com's name servers are shared with other domains, for example ligoo-app-frontend.pages.dev, rewardsdays.net, epessupplycompany.com and two more.

It is common for these name servers to be used in conjunction with the name servers ben.ns.cloudflare.com, emma.ns.cloudflare.com and zara.ns.cloudflare.com.

Host names with 6 IP numbers:

Hostname fay.ns.cloudflare.com directs to 108.162.192.115, 172.64.32.115 and 173.245.58.115 along with 3 other IP addresses.

Hostname sid.ns.cloudflare.com directs to 108.162.193.143, 172.64.33.143 and 173.245.59.143 along with 3 other IP addresses.

Mail Servers

Five mail servers handle helicontechnology.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

helicontechnology.com shares mail servers — at least in part — with other domains, including harvestandbloomsc.com, popularessentials.in, palp.tv and two others.

These mail servers are frequently used alongside mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.

Host names with two IP numbers:

aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c17::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1a IP addresses each.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.27 IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.