bitsignal.com - dns.ninja

`bitsignal.com`

DNSSEC	⚠️ Not signed
A	2606:50c0:8000::153^{🇺🇸 Fastly2606:50c0:8000::/48 88 Colin P Kelly Jr Street San Francisco CA 94107 United States}
A	2606:50c0:8001::153^{🇺🇸 Fastly2606:50c0:8001::/48 + 88 Colin P Kelly Jr Street San Francisco CA 94107 United States}
A	2606:50c0:8002::153^{🇺🇸 Fastly2606:50c0:8002::/48 + 88 Colin P Kelly Jr Street San Francisco CA 94107 United States}
A	2606:50c0:8003::153^{🇺🇸 Fastly2606:50c0:8003::/48 + 88 Colin P Kelly Jr Street San Francisco CA 94107 United States}
A	185.199.108.153^{🇺🇸 Fastly185.199.108.0/24 GitHub - 185.199.108.0/24}
A	185.199.109.153^{🇺🇸 Fastly185.199.109.0/24 GitHub - 185.199.109.0/24}
A	185.199.110.153^{🇺🇸 Fastly185.199.110.0/24 GitHub - 185.199.110.0/24}
A	185.199.111.153^{🇺🇸 Fastly185.199.111.0/24 GitHub - 185.199.111.0/24}
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com`
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	172.253.139.26^{🇺🇸 Google172.253.139.0/24}
			PTR	`yuiadsk-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-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	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`google-site-verification=GCJBcu3HqJe4u32tA1t0wAvaw2w2RKa3KyF8epUEo9M`
SOA	`ns1.digitalocean.com`hostmaster@bitsignal.com serial=0

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

Same first word

bitsignal.org

bitsignal.io

bitsignal.de

bitsignal.com

bitsignal.app

Similar names

lbaitings.de

tbsailing.com

signalbit.com

altingsib.ru

signalbit.io

ignitlabs.com

tbsailing.pl

iblasting.com

satbiling.com

blingista.com

signalbit.net

DNS History

25 records (16 active, 9 former)

○NSns-1196.awsdns-21.org2015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

○NSns-2002.awsdns-58.co.uk2015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

○NSns-313.awsdns-39.com2015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

○NSns-533.awsdns-02.net2015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

●NSns1.digitalocean.com2026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●NSns2.digitalocean.com2026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●NSns3.digitalocean.com2026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●MXalt1.aspmx.l.google.com2015-05-21 → 2026-07-05 · 3 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2026-07-05 02:31:04

●MXalt2.aspmx.l.google.com2015-05-21 → 2026-07-05 · 3 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2026-07-05 02:31:04

●MXalt3.aspmx.l.google.com2026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●MXalt4.aspmx.l.google.com2026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●MXaspmx.l.google.com2015-05-21 → 2026-07-05 · 3 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2026-07-05 02:31:04

○MXaspmx2.googlemail.com2015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

○MXaspmx3.googlemail.com2015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

○MXaspmx4.googlemail.com2015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

○MXaspmx5.googlemail.com2015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

●A185.199.108.1532026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●A185.199.109.1532026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●A185.199.110.1532026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●A185.199.111.1532026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●A2606:50c0:8000::1532026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●A2606:50c0:8001::1532026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●A2606:50c0:8002::1532026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

●A2606:50c0:8003::1532026-02-21 → 2026-07-05 · 3 obs

○ 2017-07-24 09:10:02
● 2026-02-21 01:36:40
● 2026-07-05 02:31:04

○A66.33.212.992015-05-21 → 2017-07-24 · 5 obs

○ 2008-03-20 04:55:04
● 2015-05-21 21:53:34
● 2017-07-24 09:10:02
○ 2026-02-21 01:36:40
○ 2026-07-05 02:31:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
bitsignal.com	ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com	3 records

✅ Authoritative Response

Server:172.64.52.210

NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitsignal.com (unsigned zone)

⏱️ Timing

Total: 575ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`185.199.111.153, 185.199.108.153...`
AAAA	4	`2606:50c0:8003::153, 2606:50c0:8001::153...`
NS	3	`ns1.digitalocean.com, ns2.digitalocean.com...`
MX	5	`alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	1	`google-site-verification=GCJBcu3HqJe4u32`
SOA	1	`ns1.digitalocean.com hostmaster.bitsigna`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)

Analysis

IP Addresses

bitsignal.com points to 8 IP addresses, including 185.199.108.153, 185.199.109.153 and 185.199.110.153, plus 5 other.

backlink-prospector-for-manual-outreach-and-email-templates.html.html.free-backlink-generator-builder-online.boostexchangenow.github.io, html.free-social-growth-tools.socialboostexchange.github.io, chandaarunasri.github.io plus two other host names have IP numbers in common with bitsignal.com.

Name Servers

bitsignal.com is served by three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

bitsignal.com has at least partial name server overlap with other domains, such as barefootand.com, nomenmarket.com, photosite.gr and two others.

The hostnames ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com each direct to two IP addresses — ns1.digitalocean.com to 172.64.52.210 and 2606:4700:52::ac40:34d2, ns2.digitalocean.com to 172.64.53.21 and 2606:4700:5a::ac40:3515, and ns3.digitalocean.com to 172.64.49.209 and 2606:4700:52::ac40:31d1.

Mail Servers

Mail for bitsignal.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by bitsignal.com are shared with other domains: ns500841.ns500841.ns500841.ns500794.ns500795.ns500794.ns500821.ns500821.ns500794.ns500821.ns500794.ns500790.lustypartnersfinder.com, discipleheritage.org, sportsgarage.com and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

The A records for aspmx.l.google.com return 172.253.139.26 and 2607:f8b0:4004:c1d::1b.

The A records for alt1.aspmx.l.google.com return 108.177.123.27 and 2800:3f0:4003:c0f::1b.

The A records for alt2.aspmx.l.google.com return 172.253.116.26 and 2a00:1450:400b:c02::1b.

The A records for alt3.aspmx.l.google.com return 192.178.223.27 and 2a00:1450:4009:c0f::1b.

The A records for alt4.aspmx.l.google.com return 172.253.157.26 and 2a00:1450:400c:c23::1b.