helpgo.com - dns.ninja

`helpgo.com`

DNSSEC	⚠️ Not signed
A	54.215.31.113^{🇺🇸 Amazon54.215.0.0/17 EC2 SFO prefix}
		PTR	`ec2-54-215-31-113.us-west-1.compute.amazonaws.com`
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
SOA	`ns1.dyna-ns.net`hostmaster@helpgo.com 2026-05-27 #2

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

Same first word

helpgo.com.cn

helpgo.com

Similar names

gohelp.de

phlego.com

gohelp.net

gpohle.com

phogle.com

hopgle.com

gohelp.eu

gohelp.org

gohelp.kr

gohelp.in

gophle.com

gohelp.org.uk

gohelp.co.kr

lghope.com

phogel.de

phlego.top

hpgloe.com

gohelp.com

gohelp.co.uk

gohelp.co

gohelp.sk

gpoehl.de

phogel.com

DNS History

14 records (3 active, 11 former)

○NSdns1.name-services.com2016-04-28 → 2018-09-06 · 6 obs

○ 2016-02-02 10:03:14
● 2016-04-28 22:35:20
○ 2017-01-23 09:28:22
● 2018-09-06 21:42:20
○ 2026-05-03 18:46:46
○ 2026-07-10 23:54:34

○NSdns2.name-services.com2016-04-28 → 2018-09-06 · 6 obs

○ 2016-02-02 10:03:14
● 2016-04-28 22:35:20
○ 2017-01-23 09:28:22
● 2018-09-06 21:42:20
○ 2026-05-03 18:46:46
○ 2026-07-10 23:54:34

○NSdns3.name-services.com2016-04-28 → 2018-09-06 · 6 obs

○ 2016-02-02 10:03:14
● 2016-04-28 22:35:20
○ 2017-01-23 09:28:22
● 2018-09-06 21:42:20
○ 2026-05-03 18:46:46
○ 2026-07-10 23:54:34

○NSdns4.name-services.com2016-04-28 → 2018-09-06 · 6 obs

○ 2016-02-02 10:03:14
● 2016-04-28 22:35:20
○ 2017-01-23 09:28:22
● 2018-09-06 21:42:20
○ 2026-05-03 18:46:46
○ 2026-07-10 23:54:34

○NSdns5.name-services.com2016-04-28 → 2018-09-06 · 6 obs

○ 2016-02-02 10:03:14
● 2016-04-28 22:35:20
○ 2017-01-23 09:28:22
● 2018-09-06 21:42:20
○ 2026-05-03 18:46:46
○ 2026-07-10 23:54:34

●NSns1.dyna-ns.net2026-05-03 → 2026-07-10 · 3 obs

○ 2018-09-06 21:42:20
● 2026-05-03 18:46:46
● 2026-07-10 23:54:34

○NSns1.site4now.net2015-06-16 → 2017-01-23 · 6 obs

● 2015-06-16 02:27:48
● 2016-02-02 10:03:14
○ 2016-04-28 22:35:20
● 2017-01-23 09:28:22
○ 2018-09-06 21:42:20
○ 2026-07-10 23:54:34

●NSns2.dyna-ns.net2026-05-03 → 2026-07-10 · 3 obs

○ 2018-09-06 21:42:20
● 2026-05-03 18:46:46
● 2026-07-10 23:54:34

○NSns2.site4now.net2015-06-16 → 2017-01-23 · 6 obs

● 2015-06-16 02:27:48
● 2016-02-02 10:03:14
○ 2016-04-28 22:35:20
● 2017-01-23 09:28:22
○ 2018-09-06 21:42:20
○ 2026-07-10 23:54:34

○NSns3.site4now.net2015-06-16 → 2017-01-23 · 6 obs

● 2015-06-16 02:27:48
● 2016-02-02 10:03:14
○ 2016-04-28 22:35:20
● 2017-01-23 09:28:22
○ 2018-09-06 21:42:20
○ 2026-07-10 23:54:34

○A205.144.171.1182017-01-23 → 2017-01-23 · 4 obs

○ 2016-04-28 22:35:20
● 2017-01-23 09:28:22
○ 2018-09-06 21:42:20
○ 2026-07-10 23:54:34

○A205.144.171.22015-06-16 → 2016-02-02 · 4 obs

● 2015-06-16 02:27:48
● 2016-02-02 10:03:14
○ 2016-04-28 22:35:20
○ 2026-07-10 23:54:34

●A54.215.31.1132026-05-03 → 2026-07-10 · 3 obs

○ 2018-09-06 21:42:20
● 2026-05-03 18:46:46
● 2026-07-10 23:54:34

○A98.124.199.172016-04-28 → 2018-09-06 · 6 obs

○ 2016-02-02 10:03:14
● 2016-04-28 22:35:20
○ 2017-01-23 09:28:22
● 2018-09-06 21:42:20
○ 2026-05-03 18:46:46
○ 2026-07-10 23:54:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
helpgo.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.24.5

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for helpgo.com (unsigned zone)

⏱️ Timing

Total: 351ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.215.31.113`
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.helpgo.com`

Analysis

IP Addresses

helpgo.com has exactly one IP address — 54.215.31.113.

banteng69elite.com, sinbasket.com, nexpos.com plus two other host names have IP numbers in common with helpgo.com.

Name Servers

helpgo.com is delegated to two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.

The name server configuration of helpgo.com is shared with other domains, for instance traveller.in, 07771f4f3e0add30.com, bf301v.com and two others.

Both ns1.dyna-ns.net and ns2.dyna-ns.net resolve to four IP addresses: ns1.dyna-ns.net directs to 162.159.26.92, 162.159.27.158, 2400:cb00:2049:1::a29f:1a5c and 2400:cb00:2049:1::a29f:1b9e, and ns2.dyna-ns.net directs to 162.159.24.5, 162.159.25.5, 2400:cb00:2049:1::a29f:1805 and 2400:cb00:2049:1::a29f:1905.