fameware.com - robtex.com
fameware.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.bdydns.cn ⭐ | ||||||
| A | 240e:940:603:3:0:ff:b05b:137e🇨🇳 CHINANET-BACKBONE240e:940::/32 China Telecom (Hebei) Limited | ||||||
| A | 180.97.36.63🇨🇳 ChinaNet-NANJING-JISHAN-IDC180.97.36.0/24 JS-CT NJ-JS-IDC | ||||||
| A | 183.232.231.249🇨🇳 CMNET-GuangDong-AP183.232.231.0/24 CMI (Customer Route) | ||||||
| NS | ns2.bdydns.cn | ||||||
| A | 240e:940:603:5:0:ff:b0cf:479b🇨🇳 CHINANET-BACKBONE240e:940::/32 China Telecom (Hebei) Limited | ||||||
| A | 14.215.177.154🇨🇳 CHINANET-BACKBONE14.208.0.0/12 China Telecom Network | ||||||
| A | 112.80.248.202🇨🇳 CHINA169-Backbone112.80.0.0/13 China Unicom CHINA169 Jiangsu Province Network | ||||||
| A | 119.75.222.53🇨🇳 Baidu119.75.222.0/24 | ||||||
| A | 124.237.208.58🇨🇳 CHINANET-BACKBONE124.236.0.0/14 CMI (Customer Route) | ||||||
| PTR | 58.208.237.124.broad.bd.he.dynamic.163data.com.cn | ||||||
| SOA | ns1.bdydns.cnsa@dudns.com 2018-08-01 #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.netnstld@verisign-grs.com serial=1771291435 | ||||||
Same first word
fameware.com |
Similar names
DNS History
13 records (2 active, 11 former)
○NSa.ns36.de2016-02-07 → 2016-05-29 · 5 obs
○ 2015-11-15 22:40:34
● 2016-02-07 19:36:12
● 2016-05-29 15:22:38
○ 2017-02-10 15:37:04
○ 2026-03-22 18:47:20
● 2016-02-07 19:36:12
● 2016-05-29 15:22:38
○ 2017-02-10 15:37:04
○ 2026-03-22 18:47:20
○NSb.ns36.de2016-02-07 → 2016-05-29 · 5 obs
○ 2015-11-15 22:40:34
● 2016-02-07 19:36:12
● 2016-05-29 15:22:38
○ 2017-02-10 15:37:04
○ 2026-03-22 18:47:20
● 2016-02-07 19:36:12
● 2016-05-29 15:22:38
○ 2017-02-10 15:37:04
○ 2026-03-22 18:47:20
○NSjuming.dnsdun.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-29 15:22:38
● 2017-02-10 15:37:04
○ 2020-01-03 07:11:24
○ 2026-03-22 18:47:20
● 2017-02-10 15:37:04
○ 2020-01-03 07:11:24
○ 2026-03-22 18:47:20
○NSjuming.dnsdun.net2017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-29 15:22:38
● 2017-02-10 15:37:04
○ 2020-01-03 07:11:24
○ 2026-03-22 18:47:20
● 2017-02-10 15:37:04
○ 2020-01-03 07:11:24
○ 2026-03-22 18:47:20
●NSns1.bdydns.cn2020-01-03 → 2026-03-22 · 3 obs
○ 2017-02-10 15:37:04
● 2020-01-03 07:11:24
● 2026-03-22 18:47:20
● 2020-01-03 07:11:24
● 2026-03-22 18:47:20
○NSns1.sedoparking.com2015-07-15 → 2015-11-15 · 4 obs
● 2015-07-15 12:56:46
● 2015-11-15 22:40:34
○ 2016-02-07 19:36:12
○ 2026-03-22 18:47:20
● 2015-11-15 22:40:34
○ 2016-02-07 19:36:12
○ 2026-03-22 18:47:20
●NSns2.bdydns.cn2020-01-03 → 2026-03-22 · 3 obs
○ 2017-02-10 15:37:04
● 2020-01-03 07:11:24
● 2026-03-22 18:47:20
● 2020-01-03 07:11:24
● 2026-03-22 18:47:20
○NSns2.sedoparking.com2015-07-15 → 2015-11-15 · 4 obs
● 2015-07-15 12:56:46
● 2015-11-15 22:40:34
○ 2016-02-07 19:36:12
○ 2026-03-22 18:47:20
● 2015-11-15 22:40:34
○ 2016-02-07 19:36:12
○ 2026-03-22 18:47:20
○MXmail.nickstel.com2015-07-15 → 2015-11-15 · 4 obs
● 2015-07-15 12:56:46
● 2015-11-15 22:40:34
○ 2016-02-07 19:36:12
○ 2026-03-22 18:47:20
● 2015-11-15 22:40:34
○ 2016-02-07 19:36:12
○ 2026-03-22 18:47:20
○MXmailgw.ns36.de2016-02-07 → 2016-05-29 · 5 obs
○ 2015-11-15 22:40:34
● 2016-02-07 19:36:12
● 2016-05-29 15:22:38
○ 2017-02-10 15:37:04
○ 2026-03-22 18:47:20
● 2016-02-07 19:36:12
● 2016-05-29 15:22:38
○ 2017-02-10 15:37:04
○ 2026-03-22 18:47:20
○A23.224.175.2272017-02-10 → 2017-02-10 · 4 obs
○ 2016-05-29 15:22:38
● 2017-02-10 15:37:04
○ 2020-01-03 07:11:24
○ 2026-03-22 18:47:20
● 2017-02-10 15:37:04
○ 2020-01-03 07:11:24
○ 2026-03-22 18:47:20
○A72.52.4.1192015-07-15 → 2015-11-15 · 4 obs
● 2015-07-15 12:56:46
● 2015-11-15 22:40:34
○ 2016-02-07 19:36:12
○ 2026-03-22 18:47:20
● 2015-11-15 22:40:34
○ 2016-02-07 19:36:12
○ 2026-03-22 18:47:20
○A72.52.4.902016-02-07 → 2016-05-29 · 5 obs
○ 2015-11-15 22:40:34
● 2016-02-07 19:36:12
● 2016-05-29 15:22:38
○ 2017-02-10 15:37:04
○ 2026-03-22 18:47:20
● 2016-02-07 19:36:12
● 2016-05-29 15:22:38
○ 2017-02-10 15:37:04
○ 2026-03-22 18:47:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net... | - |
| fameware.com | ns1.bdydns.cn, ns2.bdydns.cn | - |
✅ Authoritative Response
Server: 119.75.222.53
NS records: ns1.bdydns.cn, ns2.bdydns.cn
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fameware.com (unsigned zone)
⏱️ Timing
Total: 3656ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.bdydns.cn, ns2.bdydns.cn |
| SOA | 1 | ns1.bdydns.cn sa.dudns.com |
Analysis
Name Servers
fameware.com is delegated to two name servers: ns1.bdydns.cn and ns2.bdydns.cn.
fameware.com uses the same name server setup as other domains, including lituojinshu.com, shangyeguolu.com, xtpharmacy.com, ayarlab.com and cwscw.com.
Five IPs per host:
ns2.bdydns.cn points to 240e:940:603:5:0:ff:b0cf:479b, 14.215.177.154, 112.80.248.202, 119.75.222.53 and 124.237.208.58.
Three IPs per host:
ns1.bdydns.cn points to 240e:940:603:3:0:ff:b05b:137e, 180.97.36.63 and 183.232.231.249.