hellogo.com - dns.ninja

hellogo.com

DNSSEC⚠️ Not signed
NSns-1165.awsdns-17.org ⚠️ Not in zone NS records
A2600:9000:5304:8d00::1🇺🇸 Amazon2600:9000:5304::/48 - CloudFront
PTRns-1165.awsdns-17.org
A205.251.196.141🇺🇸 Amazon205.251.196.0/24 prefix
PTRns-1165.awsdns-17.org
NSns-1561.awsdns-03.co.uk ⚠️ Not in zone NS records
A2600:9000:5306:1900::1🇺🇸 Amazon2600:9000:5306::/48 - CloudFront
PTRns-1561.awsdns-03.co.uk
A205.251.198.25🇺🇸 Amazon205.251.198.0/24 prefix
PTRns-1561.awsdns-03.co.uk
NSns-290.awsdns-36.com ⚠️ Not in zone NS records
A2600:9000:5301:2200::1🇺🇸 Amazon2600:9000:5301::/48 - CloudFront
PTRns-290.awsdns-36.com
A205.251.193.34🇺🇸 Amazon205.251.193.0/24 prefix
PTRns-290.awsdns-36.com
NSns-661.awsdns-18.net ⚠️ Not in zone NS records
A2600:9000:5302:9500::1🇺🇸 Amazon2600:9000:5302::/48 - CloudFront
PTRns-661.awsdns-18.net
A205.251.194.149🇺🇸 Amazon205.251.194.0/24 prefix
PTRns-661.awsdns-18.net
NSns1-02.azure-dns.com ⚠️ Not in zone NS records
A2603:1061:0:700::2🇺🇸 Microsoft2603:1000::/25 MICROSOFT
PTRns1-02.azure-dns.com
A13.107.236.2🇺🇸 Microsoft13.104.0.0/14 MICROSOFT
PTRns1-02.azure-dns.com
NSns2-02.azure-dns.net ⚠️ Not in zone NS records
A2620:1ec:8ec:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT
PTRns2-02.azure-dns.net
A150.171.21.2🇺🇸 Microsoft150.171.0.0/16 MICROSOFT
PTRns2-02.azure-dns.net
NSns3-02.azure-dns.org ⚠️ Not in zone NS records
A2a01:111:4000:700::2🇬🇧 Microsoft2a01:111:4000::/36
PTRns3-02.azure-dns.org
A204.14.183.2🇺🇸 Microsoft204.14.180.0/22
PTRns3-02.azure-dns.org
NSns4-02.azure-dns.info ⚠️ Not in zone NS records
A2620:1ec:bda:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT
PTRns4-02.azure-dns.info
A208.84.5.2🇺🇸 Microsoft208.84.0.0/21 MICROSOFT
PTRns4-02.azure-dns.info

com

Same first word

Similar names

DNS History

20 records (8 active, 12 former)

20162017201820192020202120222023202420252026NSns-1165.awsdns-17.orgns-1561.awsdns-03.co.ukns-290.awsdns-36.comns-661.awsdns-18.netns1-02.azure-dns.comns2-02.azure-dns.netns3-02.azure-dns.orgns4-02.azure-dns.infons-fr.1and1-dns.bizns-fr.1and1-dns.comns-fr.1and1-dns.frns-fr.1and1-dns.orgns1.host-nexus.comns2.host-nexus.comMXmx00.1and1.frmx01.1and1.frsmtp-01.serveursdns.netA2001:8d8:1000:c299:1e55:8eab:7397:5801217.76.132.5487.106.155.58
NSns-1165.awsdns-17.org2026-02-22 → 2026-07-04 · 3 obs
○ 2017-05-23 14:35:28
● 2026-02-22 22:50:58
● 2026-07-04 13:29:46
NSns-1561.awsdns-03.co.uk2026-02-22 → 2026-07-04 · 3 obs
○ 2017-05-23 14:35:28
● 2026-02-22 22:50:58
● 2026-07-04 13:29:46
NSns-290.awsdns-36.com2026-02-22 → 2026-07-04 · 3 obs
○ 2017-05-23 14:35:28
● 2026-02-22 22:50:58
● 2026-07-04 13:29:46
NSns-661.awsdns-18.net2026-02-22 → 2026-07-04 · 3 obs
○ 2017-05-23 14:35:28
● 2026-02-22 22:50:58
● 2026-07-04 13:29:46
NSns-fr.1and1-dns.biz2016-04-17 → 2017-05-23 · 5 obs
○ 2016-01-24 17:10:02
● 2016-04-17 08:44:46
● 2017-05-23 14:35:28
○ 2026-02-22 22:50:58
○ 2026-07-04 13:29:46
NSns-fr.1and1-dns.com2016-04-17 → 2017-05-23 · 5 obs
○ 2016-01-24 17:10:02
● 2016-04-17 08:44:46
● 2017-05-23 14:35:28
○ 2026-02-22 22:50:58
○ 2026-07-04 13:29:46
NSns-fr.1and1-dns.fr2016-04-17 → 2017-05-23 · 5 obs
○ 2016-01-24 17:10:02
● 2016-04-17 08:44:46
● 2017-05-23 14:35:28
○ 2026-02-22 22:50:58
○ 2026-07-04 13:29:46
NSns-fr.1and1-dns.org2016-04-17 → 2017-05-23 · 5 obs
○ 2016-01-24 17:10:02
● 2016-04-17 08:44:46
● 2017-05-23 14:35:28
○ 2026-02-22 22:50:58
○ 2026-07-04 13:29:46
NSns1-02.azure-dns.com2026-02-22 → 2026-07-04 · 3 obs
○ 2017-05-23 14:35:28
● 2026-02-22 22:50:58
● 2026-07-04 13:29:46
NSns1.host-nexus.com2015-06-04 → 2016-01-24 · 4 obs
● 2015-06-04 13:24:14
● 2016-01-24 17:10:02
○ 2016-04-17 08:44:46
○ 2026-07-04 13:29:46
NSns2-02.azure-dns.net2026-02-22 → 2026-07-04 · 3 obs
○ 2017-05-23 14:35:28
● 2026-02-22 22:50:58
● 2026-07-04 13:29:46
NSns2.host-nexus.com2015-06-04 → 2016-01-24 · 4 obs
● 2015-06-04 13:24:14
● 2016-01-24 17:10:02
○ 2016-04-17 08:44:46
○ 2026-07-04 13:29:46
NSns3-02.azure-dns.org2026-02-22 → 2026-07-04 · 3 obs
○ 2017-05-23 14:35:28
● 2026-02-22 22:50:58
● 2026-07-04 13:29:46
NSns4-02.azure-dns.info2026-02-22 → 2026-07-04 · 3 obs
○ 2017-05-23 14:35:28
● 2026-02-22 22:50:58
● 2026-07-04 13:29:46
MXmx00.1and1.fr2016-04-17 → 2017-05-23 · 5 obs
○ 2016-01-24 17:10:02
● 2016-04-17 08:44:46
● 2017-05-23 14:35:28
○ 2026-02-22 22:50:58
○ 2026-07-04 13:29:46
MXmx01.1and1.fr2016-04-17 → 2017-05-23 · 5 obs
○ 2016-01-24 17:10:02
● 2016-04-17 08:44:46
● 2017-05-23 14:35:28
○ 2026-02-22 22:50:58
○ 2026-07-04 13:29:46
MXsmtp-01.serveursdns.net2015-06-04 → 2016-01-24 · 4 obs
● 2015-06-04 13:24:14
● 2016-01-24 17:10:02
○ 2016-04-17 08:44:46
○ 2026-07-04 13:29:46
A2001:8d8:1000:c299:1e55:8eab:7397:58012016-04-17 → 2017-05-23 · 5 obs
○ 2016-01-24 17:10:02
● 2016-04-17 08:44:46
● 2017-05-23 14:35:28
○ 2026-02-22 22:50:58
○ 2026-07-04 13:29:46
A217.76.132.542015-06-04 → 2016-01-24 · 4 obs
● 2015-06-04 13:24:14
● 2016-01-24 17:10:02
○ 2016-04-17 08:44:46
○ 2026-07-04 13:29:46
A87.106.155.582016-04-17 → 2017-05-23 · 5 obs
○ 2016-01-24 17:10:02
● 2016-04-17 08:44:46
● 2017-05-23 14:35:28
○ 2026-02-22 22:50:58
○ 2026-07-04 13:29:46

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comi.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net, c.gtld-servers.net...-
hellogo.comns-661.awsdns-18.net, ns-290.awsdns-36.com, ns-1561.awsdns-03.co.uk, ns-1165.awsdns-17.org...4 records

✅ Authoritative Response

Server:208.84.5.2

NS records: ns-661.awsdns-18.net, ns-290.awsdns-36.com, ns-1561.awsdns-03.co.uk, ns-1165.awsdns-17.org, ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hellogo.com (unsigned zone)

⏱️ Timing

Total: 374ms | Queries: -

📄 Records

TypeCountSample Data

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns-290.awsdns-36.com, ns-290.awsdns-36.com, ns1-02.azure-dns.com...)

Analysis

Name Servers

hellogo.com has 8 name servers — ns-290.awsdns-36.com, ns1-02.azure-dns.com, ns4-02.azure-dns.info and 5 others.

At least some of hellogo.com's name servers are shared with other domains, for example firstflirts.de, airllc.us, 200.46.207.in-addr.arpa and two more.

The name servers ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns-661.awsdns-18.net and two others are commonly seen in use alongside these name servers.

Host names that have two IP addresses:

ns-290.awsdns-36.com resolves to 205.251.193.34 and 2600:9000:5301:2200::1.

ns1-02.azure-dns.com resolves to 13.107.236.2 and 2603:1061:0:700::2.

ns4-02.azure-dns.info resolves to 208.84.5.2 and 2620:1ec:bda:700::2.

ns-661.awsdns-18.net resolves to 205.251.194.149 and 2600:9000:5302:9500::1.

ns2-02.azure-dns.net resolves to 150.171.21.2 and 2620:1ec:8ec:700::2.

ns-1165.awsdns-17.org resolves to 205.251.196.141 and 2600:9000:5304:8d00::1.

ns3-02.azure-dns.org resolves to 204.14.183.2 and 2a01:111:4000:700::2.

ns-1561.awsdns-03.co.uk resolves to 205.251.198.25 and 2600:9000:5306:1900::1.