bitcoin-message.com - dns.ninja

`bitcoin-message.com`

DNSSEC	⚠️ Not signed
A	151.101.1.195^{🇺🇸 Fastly151.101.0.0/22}
A	151.101.65.195^{🇺🇸 Fastly151.101.64.0/22}
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	`mx.yandex.net` ⭐
		A	2a02:6b8::311^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
		A	77.88.21.249^{🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
TXT	`v=spf1 redirect=_spf.yandex.net`
TXT	`google-site-verification=KpQQCXovUl17rPl4TZ5i1st2KXQT8wRLzNoCwdob0-Q`
SOA	`ns1.digitalocean.com`hostmaster@bitcoin-message.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=1785295767

Same first word

bitcoin-message.com

DNS History

11 records (6 active, 5 former)

●NSns1.digitalocean.com2026-02-27 → 2026-07-29 · 3 obs

○ 2015-12-22 22:28:32
● 2026-02-27 12:28:40
● 2026-07-29 03:42:32

○NSns1.sedoparking.com2015-05-06 → 2015-10-10 · 4 obs

● 2015-05-06 01:24:44
● 2015-10-10 04:00:22
○ 2015-12-22 22:28:32
○ 2026-07-29 03:42:32

●NSns2.digitalocean.com2026-02-27 → 2026-07-29 · 3 obs

○ 2015-12-22 22:28:32
● 2026-02-27 12:28:40
● 2026-07-29 03:42:32

○NSns2.sedoparking.com2015-05-06 → 2015-10-10 · 4 obs

● 2015-05-06 01:24:44
● 2015-10-10 04:00:22
○ 2015-12-22 22:28:32
○ 2026-07-29 03:42:32

●NSns3.digitalocean.com2026-02-27 → 2026-07-29 · 3 obs

○ 2015-12-22 22:28:32
● 2026-02-27 12:28:40
● 2026-07-29 03:42:32

○MXmail.b-io.co2015-05-06 → 2015-05-06 · 3 obs

● 2015-05-06 01:24:44
○ 2015-10-10 04:00:22
○ 2026-07-29 03:42:32

○MXmail.nickstel.com2015-10-10 → 2015-10-10 · 4 obs

○ 2015-05-06 01:24:44
● 2015-10-10 04:00:22
○ 2015-12-22 22:28:32
○ 2026-07-29 03:42:32

●MXmx.yandex.net2026-02-27 → 2026-07-29 · 3 obs

○ 2015-12-22 22:28:32
● 2026-02-27 12:28:40
● 2026-07-29 03:42:32

●A151.101.1.1952026-02-27 → 2026-07-29 · 3 obs

○ 2015-12-22 22:28:32
● 2026-02-27 12:28:40
● 2026-07-29 03:42:32

●A151.101.65.1952026-02-27 → 2026-07-29 · 3 obs

○ 2015-12-22 22:28:32
● 2026-02-27 12:28:40
● 2026-07-29 03:42:32

○A72.52.4.912015-05-06 → 2015-10-10 · 4 obs

● 2015-05-06 01:24:44
● 2015-10-10 04:00:22
○ 2015-12-22 22:28:32
○ 2026-07-29 03:42:32

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:172.64.49.209

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitcoin-message.com (unsigned zone)

⏱️ Timing

Total: 290ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`151.101.65.195, 151.101.1.195`
NS	3	`ns2.digitalocean.com, ns1.digitalocean.com...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	2	`v=spf1 redirect=_spf.yandex.net, google-site-verification=KpQQCXovUl17rPl`
SOA	1	`ns1.digitalocean.com hostmaster.bitcoin-`

📌 Glue Records Collected

Total: 3

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

Analysis

IP Addresses

bitcoin-message.com points to the IP addresses 151.101.1.195 and 151.101.65.195

ninja.usestrive.com, bitcoin.work, labelmeister.co plus two other host names have IP numbers in common with bitcoin-message.com.

Name Servers

Three name servers are authoritative for bitcoin-message.com: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

There is at least partial name server overlap between bitcoin-message.com and other domains — carmoo.com, imsmemory.com.au, ciess.org and two more among them.

ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2. ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515. ns3.digitalocean.com resolves to 172.64.49.209 and 2606:4700:52::ac40:31d1. All three hostnames point to two IP numbers each.

Mail Servers

bitcoin-message.com uses one mail server — mx.yandex.net.

The mail server setup of bitcoin-message.com matches that of other domains such as atoc.ru, www.musichall27.ru, avtobus.online and two others.

bitcoin-message.com and a number of other domains — krishnatraders.com.np, nordsteel.ru, progressiv.su and markacanavari.com among them — share at least some of the same mail servers.

mx.yandex.net carries two IP numbers: 77.88.21.249 and 2a02:6b8::311.