`bitcoinassociation.com`

DNSSEC	⚠️ Not signed
A	217.19.248.132^{🇬🇧 SAFENAMES-AS217.19.248.0/24 Safenames Datacentre}
		PTR	`redirect.idp365.net`
NS	`dns1.idp365.net` ⭐
		A	2001:19f0:7402:41a:5400:2ff:feb8:7a47^{🇬🇧 AS-VULTR2001:19f0:7400::/38 Vultr Assigned Prefix}
			PTR	`dns1.idp365.net`
		A	188.208.34.10^{🇬🇧 SAFENAMES-AS188.208.34.0/24 Safenames Ltd}
			PTR	`dns1.idp365.net`
NS	`dns2.idp365.net`
		A	2001:19f0:7400:8f60:5400:2ff:fec3:21f8^{🇬🇧 AS-VULTR2001:19f0:7400::/38 Vultr Assigned Prefix}
			PTR	`dist05-dns3.idp365.net`
		A	93.115.247.10^{🇬🇧 SAFENAMES-AS93.115.247.0/24 Safenames Ltd}
			PTR	`dns2.idp365.net`
NS	`dns3.idp365.net`
		A	2a00:a900:6afe:1::1^{🇬🇧 SAFENAMES-AS2a00:a900:6afe::/48 Proxy route}
			PTR	`dns3.idp365.net`
		A	92.114.80.10^{🇬🇧 SAFENAMES-AS92.114.80.0/24 Safenames Ltd}
			PTR	`dns3.idp365.net`
TXT	`v=spf1 -all`
SOA	`dns1.idp365.net`hostmaster@idp365.net 2019-12-12 #1

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

Same first word

bitcoinassociation.net

bitcoinassociation.ch

DNS History

8 records (4 active, 4 former)

○NSdns1.cnomy.com2015-06-17 → 2017-08-20 · 4 obs

● 2015-06-17 00:55:18
● 2017-08-20 01:29:28
○ 2026-03-18 17:45:24
○ 2026-03-18 17:45:26

●NSdns1.idp365.net2026-03-18 → 2026-03-18 · 3 obs

○ 2017-08-20 01:29:28
● 2026-03-18 17:45:24
● 2026-03-18 17:45:26

○NSdns2.cnomy.com2015-06-17 → 2017-08-20 · 4 obs

● 2015-06-17 00:55:18
● 2017-08-20 01:29:28
○ 2026-03-18 17:45:24
○ 2026-03-18 17:45:26

●NSdns2.idp365.net2026-03-18 → 2026-03-18 · 3 obs

○ 2017-08-20 01:29:28
● 2026-03-18 17:45:24
● 2026-03-18 17:45:26

●NSdns3.idp365.net2026-03-18 → 2026-03-18 · 3 obs

○ 2017-08-20 01:29:28
● 2026-03-18 17:45:24
● 2026-03-18 17:45:26

○A208.91.196.1752015-06-17 → 2017-08-20 · 4 obs

● 2015-06-17 00:55:18
● 2017-08-20 01:29:28
○ 2026-03-18 17:45:24
○ 2026-03-18 17:45:26

●A217.19.248.1322026-03-18 → 2026-03-18 · 3 obs

○ 2017-08-20 01:29:28
● 2026-03-18 17:45:24
● 2026-03-18 17:45:26

○PTRdns1.cnomy.com2017-08-20 → 2017-08-20 · 3 obs

● 2017-08-20 01:29:28
○ 2026-03-18 17:45:24
○ 2026-03-18 17:45:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, m.gtld-servers.net, k.gtld-servers.net, i.gtld-servers.net...	-
bitcoinassociation.com	dns1.idp365.net, dns2.idp365.net, dns3.idp365.net	-

✅ Authoritative Response

Server: 188.208.34.10

NS records: dns1.idp365.net, dns2.idp365.net, dns3.idp365.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitcoinassociation.com (unsigned zone)

⏱️ Timing

Total: 914ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`217.19.248.132`
NS	3	`dns2.idp365.net, dns3.idp365.net...`
TXT	1	`v=spf1 -all`
SOA	1	`dns1.idp365.net hostmaster.idp365.net`

Analysis

IP Addresses

bitcoinassociation.com points to a single IP address: 217.19.248.132.

Other host names such as bexseroclaims.com, duke.clothing, 888games.fr, www.webroost.net and caravanholiday.ca share IP numbers with bitcoinassociation.com.

Name Servers

bitcoinassociation.com is delegated to three name servers: dns1.idp365.net, dns2.idp365.net and dns3.idp365.net.

At least part of the name servers for bitcoinassociation.com are shared with other domains, for instance visualcomputing.com.ua, tokeninc.kz, kavo.se, gsyuasaeurope.com and nvidia.systems.

Host names with two IP numbers:

dns1.idp365.net points to 2001:19f0:7402:41a:5400:2ff:feb8:7a47 and 188.208.34.10

dns2.idp365.net points to 2001:19f0:7400:8f60:5400:2ff:fec3:21f8 and 93.115.247.10

dns3.idp365.net points to 2a00:a900:6afe:1::1 and 92.114.80.10

bitcoinassociation.com - robtex.com