ruby-china.com - dns.ninja

`ruby-china.com`

DNSSEC	⚠️ Not signed
A	119.45.236.142^{🇨🇳 TENCENT-NET-AP119.45.224.0/20}
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	`f1g1ns2.dnspod.net`
		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	106.39.207.235^{🇨🇳 CHINA-1106.39.192.0/19 China Telecom Beijing Co. Ltd.}
		A	111.206.98.235^{🇨🇳 CHINA169-BJ111.206.98.0/24}
		A	220.196.136.35^{🇨🇳 UNICOM-SHFT-IDC220.196.136.0/24}
SOA	`f1g1ns1.dnspod.net`freednsadmin@dnspod.com serial=1784562847

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

WOT: UNKNOWN (2/100)
📈 Tranco rank: #356,922

Subdomains

gems.ruby-china.com

index.ruby-china.com

Same first word

ruby-china.com

ruby-china.github.io

ruby-china.org

DNS History

17 records (3 active, 14 former)

●NSf1g1ns1.dnspod.net2016-04-15 → 2026-07-27 · 3 obs

○ 2016-01-26 17:35:18
● 2016-04-15 04:58:12
● 2026-07-27 07:26:28

●NSf1g1ns2.dnspod.net2016-04-15 → 2026-07-27 · 3 obs

○ 2016-01-26 17:35:18
● 2016-04-15 04:58:12
● 2026-07-27 07:26:28

○NSns1.domain-resolution.net2015-06-08 → 2016-01-26 · 4 obs

● 2015-06-08 08:09:44
● 2016-01-26 17:35:18
○ 2016-04-15 04:58:12
○ 2026-07-27 07:26:28

○NSns2bkr.domain-resolution.net2015-11-03 → 2015-11-03 · 4 obs

○ 2015-06-08 08:09:44
● 2015-11-03 08:56:40
○ 2016-01-26 17:35:18
○ 2026-07-27 07:26:28

○NSns3.domain-resolution.net2015-11-03 → 2015-11-03 · 4 obs

○ 2015-06-08 08:09:44
● 2015-11-03 08:56:40
○ 2016-01-26 17:35:18
○ 2026-07-27 07:26:28

○NSns4ksy.domain-resolution.net2015-11-03 → 2015-11-03 · 4 obs

○ 2015-06-08 08:09:44
● 2015-11-03 08:56:40
○ 2016-01-26 17:35:18
○ 2026-07-27 07:26:28

○MXalt1.aspmx.l.google.com2016-04-15 → 2017-02-18 · 4 obs

● 2016-04-15 04:58:12
● 2017-02-18 23:07:16
○ 2020-01-01 06:18:34
○ 2026-07-27 07:26:28

○MXalt2.aspmx.l.google.com2016-04-15 → 2017-02-18 · 4 obs

● 2016-04-15 04:58:12
● 2017-02-18 23:07:16
○ 2020-01-01 06:18:34
○ 2026-07-27 07:26:28

○MXaspmx.l.google.com2016-04-15 → 2017-02-18 · 4 obs

● 2016-04-15 04:58:12
● 2017-02-18 23:07:16
○ 2020-01-01 06:18:34
○ 2026-07-27 07:26:28

○MXaspmx2.googlemail.com2016-04-15 → 2017-02-18 · 4 obs

● 2016-04-15 04:58:12
● 2017-02-18 23:07:16
○ 2020-01-01 06:18:34
○ 2026-07-27 07:26:28

○MXaspmx3.googlemail.com2016-04-15 → 2017-02-18 · 4 obs

● 2016-04-15 04:58:12
● 2017-02-18 23:07:16
○ 2020-01-01 06:18:34
○ 2026-07-27 07:26:28

○MXmx.ifaxin.org2017-02-18 → 2017-02-18 · 4 obs

○ 2016-04-15 04:58:12
● 2017-02-18 23:07:16
○ 2020-01-01 06:18:34
○ 2026-07-27 07:26:28

●A119.45.236.1422026-03-18 → 2026-07-27 · 3 obs

○ 2020-01-01 06:18:34
● 2026-03-18 20:00:04
● 2026-07-27 07:26:28

○A61.174.15.1672016-04-15 → 2017-02-18 · 5 obs

○ 2016-01-26 17:35:18
● 2016-04-15 04:58:12
● 2017-02-18 23:07:16
○ 2020-01-01 06:18:34
○ 2026-07-27 07:26:28

○A69.64.147.2422015-06-08 → 2016-01-26 · 5 obs

● 2015-06-08 08:09:44
○ 2015-11-03 08:56:40
● 2016-01-26 17:35:18
○ 2016-04-15 04:58:12
○ 2026-07-27 07:26:28

○CNAMEruby-china-redirect.b0.aicdn.com2020-01-01 → 2020-01-01 · 4 obs

○ 2017-02-18 23:07:16
● 2020-01-01 06:18:34
○ 2026-03-18 20:00:04
○ 2026-07-27 07:26:28

○CNAMEruby-china.org2016-04-15 → 2017-02-18 · 4 obs

● 2016-04-15 04:58:12
● 2017-02-18 23:07:16
○ 2020-01-01 06:18:34
○ 2026-07-27 07:26:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, f.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net...	-
ruby-china.com	f1g1ns1.dnspod.net, f1g1ns2.dnspod.net	-

✅ Authoritative Response

Server:111.206.98.235

NS records: f1g1ns1.dnspod.net, f1g1ns2.dnspod.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ruby-china.com (unsigned zone)

⏱️ Timing

Total: 542ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`119.45.236.142`
NS	2	`f1g1ns1.dnspod.net, f1g1ns2.dnspod.net`
SOA	1	`f1g1ns1.dnspod.net freednsadmin.dnspod.c`

Analysis

Hierarchy

ruby-china.com is the parent domain of gems.ruby-china.com and index.ruby-china.com.

IP Addresses

ruby-china.com points to a single IP number: 119.45.236.142.

Name Servers

The NS records for ruby-china.com delegate to f1g1ns1.dnspod.net and f1g1ns2.dnspod.net.

ruby-china.com shares its name server setup with other domains, including ruyihe.com, pc8.com, fjry.cn and two others.

At least some of ruby-china.com's name servers are shared with other domains, for example shangjuyuan.com, cxhp.cn, stop.ink and two more.

It is common for these name servers to be used in conjunction with the name servers a.dnspod.com, c.dnspod.com and b.dnspod.com.

Host names with 8 IP numbers:

f1g1ns2.dnspod.net maps to 1.12.0.1, 1.13.76.35, 36.155.149.35 and 5 additional IP addresses.

Host names with 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.