`bitrings.com`

DNSSEC	⚠️ Not signed
NS	`f1g1ns1.dnspod.net` ⭐
		A	2402:4e00:1470:2::e^{🇨🇳 TENCENT-NET-AP2402:4e00:1400::/40}
		A	1.12.0.4^{🇨🇳 TENCENT-NET-AP-CN1.12.0.0/20 ZL-IDC-BOM}
		A	1.14.119.35^{🇨🇳 TENCENT-NET-AP1.14.64.0/18}
		A	111.13.13.35^{🇨🇳 CHINAMOBILE-CN111.13.0.0/16 CMI (Customer Route)}
		A	117.135.128.235^{🇨🇳 CHINAMOBILE-CN117.135.128.0/24 CMI (Customer Route)}
			PTR	`(root)`
		A	125.94.59.235^{🇨🇳 CHINANET-BACKBONE125.88.0.0/13 chinanet Guangdong network}
		A	163.177.5.35^{🇨🇳 UNICOM-GuangZhou-IDC163.177.5.0/24}
NS	`gin.dnspod.net` ⚠️ Not in zone NS records
		A	2402:4e00:111:fff::c^{🇨🇳 TENCENT-NET-AP2402:4e00::/35}
		A	1.12.0.1^{🇨🇳 TENCENT-NET-AP-CN1.12.0.0/20 ZL-IDC-BOM}
		A	1.13.76.35^{🇨🇳 TENCENT-NET-AP1.13.64.0/18}
		A	36.155.149.35^{🇨🇳 CMNET-Jiangsu-AP36.155.144.0/21 CMI (Customer Route)}
		A	101.227.168.35^{🇨🇳 SHANGHAITELECOM101.227.168.0/23 SHIDC}
		A	111.206.98.235^{🇨🇳 CHINA169-BJ111.206.98.0/24}
NS	`open.dnspod.net` ⚠️ Not in zone NS records
		A	2402:4e00:1470:2::e^{🇨🇳 TENCENT-NET-AP2402:4e00:1400::/40}
		A	1.12.0.4^{🇨🇳 TENCENT-NET-AP-CN1.12.0.0/20 ZL-IDC-BOM}
		A	1.14.119.35^{🇨🇳 TENCENT-NET-AP1.14.64.0/18}
		A	111.13.13.35^{🇨🇳 CHINAMOBILE-CN111.13.0.0/16 CMI (Customer Route)}
		A	117.89.178.35^{🇨🇳 ChinaNet-NANJING-JISHAN-IDC117.89.176.0/21 JS-CT NJ-JS-IDC}
		A	220.196.136.35^{🇨🇳 UNICOM-SHFT-IDC220.196.136.0/24}
SOA	`f1g1ns1.dnspod.net`nxdomainadmin@dnspod.com serial=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=1783250731

WOT: SAFE (63/100)

Same first word

bitrings.com

Similar names

gritbins.co.uk

gritbins.net

DNS History

9 records (3 active, 6 former)

●NSf1g1ns1.dnspod.net2015-09-04 → 2026-07-05 · 7 obs

○ 2008-03-18 17:24:32
● 2015-09-04 00:43:08
● 2017-01-06 12:07:08
○ 2017-08-25 00:03:26
○ 2018-07-04 13:31:00
● 2026-06-28 10:51:02
● 2026-07-05 11:57:54

○NSf1g1ns2.dnspod.net2015-09-04 → 2017-01-06 · 5 obs

○ 2008-03-18 17:24:32
● 2015-09-04 00:43:08
● 2017-01-06 12:07:08
○ 2017-08-25 00:03:26
○ 2026-07-05 11:57:54

●NSgin.dnspod.net2026-06-28 → 2026-07-05 · 3 obs

○ 2018-07-04 13:31:00
● 2026-06-28 10:51:02
● 2026-07-05 11:57:54

○NSns6.cnmsn.net2008-03-18 → 2008-03-18 · 3 obs

● 2008-03-18 17:24:32
○ 2015-09-04 00:43:08
○ 2026-07-05 11:57:54

●NSopen.dnspod.net2026-06-28 → 2026-07-05 · 3 obs

○ 2018-07-04 13:31:00
● 2026-06-28 10:51:02
● 2026-07-05 11:57:54

○MXmail.bitrings.com2008-03-18 → 2008-03-18 · 3 obs

● 2008-03-18 17:24:32
○ 2015-09-04 00:43:08
○ 2026-07-05 11:57:54

○MXmx.ym.163.com2015-09-04 → 2016-12-26 · 5 obs

○ 2008-03-18 17:24:32
● 2015-09-04 00:43:08
● 2016-12-26 17:37:38
○ 2017-08-25 00:03:26
○ 2026-07-05 11:57:54

○A218.249.45.1962015-09-04 → 2016-03-03 · 5 obs

○ 2008-03-18 17:24:32
● 2015-09-04 00:43:08
● 2016-03-03 19:51:32
○ 2016-05-04 08:52:20
○ 2026-07-05 11:57:54

○A218.249.45.2002016-05-04 → 2016-12-26 · 5 obs

○ 2016-03-03 19:51:32
● 2016-05-04 08:52:20
● 2016-12-26 17:37:38
○ 2017-08-25 00:03:26
○ 2026-07-05 11:57:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net...	-
bitrings.com	open.dnspod.net, gin.dnspod.net	-

✅ Authoritative Response

Server:111.206.98.235

NS records: open.dnspod.net, gin.dnspod.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitrings.com (unsigned zone)

⏱️ Timing

Total: 985ms | Queries: -

📄 Records

Type	Count	Sample Data
SOA	1	`f1g1ns1.dnspod.net nxdomainadmin.dnspod.`

Analysis

Name Servers

bitrings.com is served by three name servers: f1g1ns1.dnspod.net, gin.dnspod.net and open.dnspod.net.

There is at least partial name server overlap between bitrings.com and other domains — logoonline.ru, 5inmg.cn, diqigan.cn and two more among them.

These name servers are routinely deployed together with the name servers f1g1ns2.dnspod.net.

Host names resolving to 7 IP numbers:

f1g1ns1.dnspod.net maps to 1.12.0.4, 1.14.119.35, 111.13.13.35 and 4 additional IP addresses.

Host names resolving to 6 IP numbers:

gin.dnspod.net maps to 1.12.0.1, 1.13.76.35, 36.155.149.35 and 3 additional IP addresses.

open.dnspod.net maps to 1.12.0.4, 1.14.119.35, 111.13.13.35 and 3 additional IP addresses.

f1g1ns1.dnspod.net and open.dnspod.net each have 2402:4e00:1470:2::e IP addresses.

f1g1ns1.dnspod.net and open.dnspod.net each have 1.12.0.4 IP addresses.

f1g1ns1.dnspod.net and open.dnspod.net each have 1.14.119.35 IP addresses.

f1g1ns1.dnspod.net and open.dnspod.net each have 111.13.13.35 IP addresses.