hubnode.com - dns.ninja

hubnode.com

DNSSEC⚠️ Not signed
A16.16.61.220🇸🇪 Amazon16.16.0.0/16 EC2 ARN Prefix
PTRec2-16-16-61-220.eu-north-1.compute.amazonaws.com
NSdns1.registrar-servers.com
A2610:a1:1024::200🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar
PTRdns1.namecheaphosting.com
PTRdns1.registrar-servers.com
A156.154.132.200🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar
PTRdns1.namecheaphosting.com
PTRdns1.registrar-servers.com
NSdns2.registrar-servers.com
A2610:a1:1025::200🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar
PTRdns2.namecheaphosting.com
PTRdns2.registrar-servers.com
A156.154.133.200🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar
PTRdns2.namecheaphosting.com
PTRdns2.registrar-servers.com
MXaspmx.l.google.com
A2607:f8b0:4004:c23::1b🇺🇸 Google2607:f8b0:4004::/48
PTRyuiadrs-in-f27.1e100.net
A142.251.167.26🇺🇸 Google142.251.167.0/24
PTRww-in-f26.1e100.net
MXalt1.aspmx.l.google.com(5)
A2800:3f0:4003:c0f::1a🇨🇱 Google2800:3f0:4003::/48
A108.177.123.26🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f26.1e100.net
MXalt2.aspmx.l.google.com(5)
A2a00:1450:400b:c02::1b🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f27.1e100.net
A172.253.116.26🇺🇸 Google172.253.116.0/24
PTRdj-in-f26.1e100.net
MXaspmx2.googlemail.com(10)
A2800:3f0:4003:c0f::1b🇨🇱 Google2800:3f0:4003::/48
A108.177.123.26🇺🇸 Google108.177.123.0/24
PTRlcscld-in-f26.1e100.net
MXaspmx3.googlemail.com(10)
A2a00:1450:400b:c02::1b🇮🇪 Google2a00:1450:400b::/48
PTRdj-in-f27.1e100.net
A172.253.116.26🇺🇸 Google172.253.116.0/24
PTRdj-in-f26.1e100.net
TXTgoogle-site-verification=hPxZ0YUE_6vjRec5cUhLPWzuJ4MMZxzDVsXorEWTdL0
SOAdns1.registrar-servers.comhostmaster@registrar-servers.com serial=1739209084

com

Same first word

Similar names

DNS History

15 records (8 active, 7 former)

20162017201820192020202120222023202420252026NSdns1.registrar-servers.comdns2.registrar-servers.comdns1.namecheaphosting.comdns2.namecheaphosting.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.commail.hubnode.comsmx1.web-hosting.comsmx2.web-hosting.comsmx3.web-hosting.comA16.16.61.220162.213.253.14
NSdns1.namecheaphosting.com2015-06-08 → 2017-06-01 · 4 obs
● 2015-06-08 20:06:40
● 2017-06-01 11:31:04
○ 2026-03-28 21:36:54
○ 2026-07-04 10:57:42
NSdns1.registrar-servers.com2026-03-28 → 2026-07-04 · 3 obs
○ 2017-06-01 11:31:04
● 2026-03-28 21:36:54
● 2026-07-04 10:57:42
NSdns2.namecheaphosting.com2015-06-08 → 2017-06-01 · 4 obs
● 2015-06-08 20:06:40
● 2017-06-01 11:31:04
○ 2026-03-28 21:36:54
○ 2026-07-04 10:57:42
NSdns2.registrar-servers.com2026-03-28 → 2026-07-04 · 3 obs
○ 2017-06-01 11:31:04
● 2026-03-28 21:36:54
● 2026-07-04 10:57:42
MXalt1.aspmx.l.google.com2026-03-28 → 2026-07-04 · 3 obs
○ 2017-06-01 11:31:04
● 2026-03-28 21:36:54
● 2026-07-04 10:57:42
MXalt2.aspmx.l.google.com2026-03-28 → 2026-07-04 · 3 obs
○ 2017-06-01 11:31:04
● 2026-03-28 21:36:54
● 2026-07-04 10:57:42
MXaspmx.l.google.com2026-03-28 → 2026-07-04 · 3 obs
○ 2017-06-01 11:31:04
● 2026-03-28 21:36:54
● 2026-07-04 10:57:42
MXaspmx2.googlemail.com2026-03-28 → 2026-07-04 · 3 obs
○ 2017-06-01 11:31:04
● 2026-03-28 21:36:54
● 2026-07-04 10:57:42
MXaspmx3.googlemail.com2026-03-28 → 2026-07-04 · 3 obs
○ 2017-06-01 11:31:04
● 2026-03-28 21:36:54
● 2026-07-04 10:57:42
MXmail.hubnode.com2015-06-08 → 2016-04-13 · 4 obs
● 2015-06-08 20:06:40
● 2016-04-13 14:49:22
○ 2016-11-26 01:26:06
○ 2026-07-04 10:57:42
MXsmx1.web-hosting.com2016-11-26 → 2017-06-01 · 5 obs
○ 2016-04-13 14:49:22
● 2016-11-26 01:26:06
● 2017-06-01 11:31:04
○ 2026-03-28 21:36:54
○ 2026-07-04 10:57:42
MXsmx2.web-hosting.com2016-11-26 → 2017-06-01 · 5 obs
○ 2016-04-13 14:49:22
● 2016-11-26 01:26:06
● 2017-06-01 11:31:04
○ 2026-03-28 21:36:54
○ 2026-07-04 10:57:42
MXsmx3.web-hosting.com2016-11-26 → 2017-06-01 · 5 obs
○ 2016-04-13 14:49:22
● 2016-11-26 01:26:06
● 2017-06-01 11:31:04
○ 2026-03-28 21:36:54
○ 2026-07-04 10:57:42
A16.16.61.2202026-03-28 → 2026-07-04 · 3 obs
○ 2017-06-01 11:31:04
● 2026-03-28 21:36:54
● 2026-07-04 10:57:42
A162.213.253.142015-06-08 → 2017-06-01 · 4 obs
● 2015-06-08 20:06:40
● 2017-06-01 11:31:04
○ 2026-03-28 21:36:54
○ 2026-07-04 10:57:42

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
hubnode.comdns1.registrar-servers.com, dns2.registrar-servers.com4 records

✅ Authoritative Response

Server:156.154.133.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hubnode.com (unsigned zone)

⏱️ Timing

Total: 176ms | Queries: -

📄 Records

TypeCountSample Data
A116.16.61.220
NS2dns1.registrar-servers.com, dns2.registrar-servers.com
MX5aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...
TXT1google-site-verification=hPxZ0YUE_6vjRec
SOA1dns1.registrar-servers.com hostmaster.re

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

IP Addresses

hubnode.com has exactly one IP address — 16.16.61.220.

ec2-16-16-61-220.eu-north-1.compute.amazonaws.com, for instance, is one of the other host names sharing IP numbers with hubnode.com.

Name Servers

hubnode.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.

The name server configuration of hubnode.com is shared with other domains, for instance mediacaffeshq.shop, otomatto.com, jupiterhost.com and two others.

hubnode.com has a partial name server overlap with other domains — among them justethicalplatinum.com and prinafrica.com.

These name servers tend to appear together with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.

The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.

Mail Servers

Mail for hubnode.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

At least some of the mail servers used by hubnode.com are shared with other domains: ns500734.ns500699.ns500699.ns500699.ns500699.ns500699.ns500699.ns500699.ns500693.ns500699.ns500699.ns500588.ns500588.ns500632.ns500588.ns500578.ns500110.dtrkdll.com, ns500693.ns500734.ns500693.ns500734.ns500734.ns500699.ns500693.ns500699.ns500632.ns500612.ns500588.ns500612.ns500612.ns500588.ns500588.dtrkdll.com, ns500758.ns500758.ns500698.ns500759.ns500698.ns500698.ns500698.ns500708.ns500576.ns500708.ns500619.ns500698.trackreceptor.com and two others among them.

These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.

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

aspmx.l.google.com directs traffic to 142.251.167.26 and 2607:f8b0:4004:c23::1b.

alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::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 108.177.123.26 IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.

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