bellcomputing.com - dns.ninja

`bellcomputing.com`

DNSSEC	⚠️ Not signed
NS	`dns1.registrar-servers.com` ⭐
		A	2610:a1:1024::200^{🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
		A	156.154.132.200^{🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
NS	`dns2.registrar-servers.com`
		A	2610:a1:1025::200^{🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
		A	156.154.133.200^{🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com -all`
TXT	`google-site-verification=ez8I_WK5kD_smd_SLPpI2ywf1QXhCy-XblJP_fRzb8Y`
SOA	`dns1.registrar-servers.com`hostmaster@registrar-servers.com serial=1776766657

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

Same first word

bellcomputing.com

DNS History

13 records (7 active, 6 former)

●NSdns1.registrar-servers.com2015-06-23 → 2026-08-03 · 3 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2026-08-03 05:25:30

●NSdns2.registrar-servers.com2015-06-23 → 2026-08-03 · 3 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2026-08-03 05:25:30

○NSdns3.registrar-servers.com2015-06-23 → 2017-04-10 · 5 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2017-04-10 21:52:58
○ 2026-04-23 02:30:18
○ 2026-08-03 05:25:30

○NSdns4.registrar-servers.com2015-06-23 → 2017-04-10 · 5 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2017-04-10 21:52:58
○ 2026-04-23 02:30:18
○ 2026-08-03 05:25:30

○NSdns5.registrar-servers.com2015-06-23 → 2017-04-10 · 5 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2017-04-10 21:52:58
○ 2026-04-23 02:30:18
○ 2026-08-03 05:25:30

●MXalt1.aspmx.l.google.com2015-06-23 → 2026-08-03 · 3 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2026-08-03 05:25:30

●MXalt2.aspmx.l.google.com2015-06-23 → 2026-08-03 · 3 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2026-08-03 05:25:30

●MXaspmx.l.google.com2015-06-23 → 2026-08-03 · 3 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2026-08-03 05:25:30

●MXaspmx2.googlemail.com2015-06-23 → 2026-08-03 · 3 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2026-08-03 05:25:30

●MXaspmx3.googlemail.com2015-06-23 → 2026-08-03 · 3 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2026-08-03 05:25:30

○A100.0.100.2242016-09-22 → 2017-04-10 · 5 obs

○ 2016-03-14 14:16:02
● 2016-09-22 18:59:00
● 2017-04-10 21:52:58
○ 2026-04-23 02:30:18
○ 2026-08-03 05:25:30

○A72.93.81.792015-06-23 → 2015-10-30 · 5 obs

○ 2008-03-19 03:07:06
● 2015-06-23 08:17:00
● 2015-10-30 16:34:24
○ 2016-03-14 14:16:02
○ 2026-08-03 05:25:30

○A96.237.144.1792016-03-14 → 2016-03-14 · 4 obs

○ 2015-10-30 16:34:24
● 2016-03-14 14:16:02
○ 2016-09-22 18:59:00
○ 2026-08-03 05:25:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, c.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net...	-
bellcomputing.com	dns1.registrar-servers.com, dns2.registrar-servers.com	4 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 bellcomputing.com (unsigned zone)

⏱️ Timing

Total: 202ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`dns1.registrar-servers.com, dns2.registrar-servers.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`v=spf1 include:_spf.google.com -all, google-site-verification=ez8I_WK5kD_smd_`
SOA	1	`dns1.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

Name Servers

bellcomputing.com is served by two delegated name servers, dns1.registrar-servers.com and dns2.registrar-servers.com.

bellcomputing.com shares its NS records with other domains, for example meetamonk.com, mylabelone.com, infonetnow.com and two others.

bellcomputing.com and other domains like aidennoble.net, electricabac.us and simulationsource.com share some name servers

These name servers are frequently paired with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.

Each of the two host names carries two IP addresses: dns1.registrar-servers.com points to 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com points to 156.154.133.200 and 2610:a1:1025::200.

Mail Servers

bellcomputing.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between bellcomputing.com and other domains, including legionmetal.com, sxmsir.com, ns500698.ns500759.ns500759.ns500759.ns500736.ns500698.ns500698.ns500736.ns500576.ns500708.ns500576.ns500619.ns500576.ns500576.ns500652.trackreceptor.com and two others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com maps to two IP addresses — 64.233.180.26 and 2607:f8b0:4004:c1f::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.

These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 2800:3f0:4003:c0f::1a IP addresses.

These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 2a00:1450:400b:c02::1a IP addresses.

These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 172.253.116.27 IP addresses.