femo.cn - robtex.com
femo.cn
| DNSSEC | ⚠️ Not signed | ||||||
| NS | pk3.22.cn ⚠️ Not in zone NS records | ||||||
| NS | pk4.22.cn ⚠️ Not in zone NS records | ||||||
| A | 39.101.68.48🇨🇳 Alibaba-Cloud39.100.0.0/14 CT BeiJing IDC | ||||||
cn
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.cn ⭐ | ||||||
| NS | b.dns.cn | ||||||
| NS | c.dns.cn | ||||||
| NS | d.dns.cn | ||||||
| NS | e.dns.cn | ||||||
| NS | ns.cernet.net ⚠️ Not in parent delegation | ||||||
| SOA | a.dns.cnroot@cnnic.cn serial=2035002086 | ||||||
Same first word
femo.hu |
femo.pt |
femo.it |
femo.org |
femo.ca |
femo.com |
femo.dk |
femo.co.za |
femo.eu |
femo.online |
femo.lv |
femo.lu |
femo.jp |
femo.be |
femo.cn |
femo.site |
Similar names
DNS History
24 records (2 active, 22 former)
○NSns1.above.com2017-02-17 → 2017-02-17 · 3 obs
● 2017-02-17 06:40:36
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
○NSns2.above.com2017-02-17 → 2017-02-17 · 3 obs
● 2017-02-17 06:40:36
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
●NSpk3.22.cn2026-07-01 → 2026-07-04 · 3 obs
○ 2017-02-17 06:40:36
● 2026-07-01 00:40:22
● 2026-07-04 13:07:08
● 2026-07-01 00:40:22
● 2026-07-04 13:07:08
●NSpk4.22.cn2026-07-01 → 2026-07-04 · 3 obs
○ 2017-02-17 06:40:36
● 2026-07-01 00:40:22
● 2026-07-04 13:07:08
● 2026-07-01 00:40:22
● 2026-07-04 13:07:08
○MXmx92.m1bp.com2017-02-17 → 2017-02-17 · 3 obs
● 2017-02-17 06:40:36
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
○MXmx92.mb5p.com2017-02-17 → 2017-02-17 · 3 obs
● 2017-02-17 06:40:36
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
○A103.218.240.1842026-07-01 → 2026-07-01 · 4 obs
○ 2017-02-17 06:40:36
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
○A103.224.182.2422017-02-17 → 2017-02-17 · 4 obs
○ 2016-05-30 08:48:44
● 2017-02-17 06:40:36
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
● 2017-02-17 06:40:36
○ 2026-07-01 00:40:22
○ 2026-07-04 13:07:08
○A118.193.33.2202026-07-01 → 2026-07-01 · 4 obs
○ 2017-02-17 06:40:36
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
○A118.193.37.942026-07-01 → 2026-07-01 · 4 obs
○ 2017-02-17 06:40:36
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
○A152.32.171.652026-07-01 → 2026-07-01 · 4 obs
○ 2017-02-17 06:40:36
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
○A154.85.60.1502026-07-01 → 2026-07-01 · 4 obs
○ 2017-02-17 06:40:36
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
● 2026-07-01 00:40:22
○ 2026-07-03 16:09:40
○ 2026-07-04 13:07:08
○A162.251.5.1872016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.522016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.532016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.542016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.552016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.562016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.572016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.582016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.592016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A45.116.62.602016-05-30 → 2016-05-30 · 4 obs
○ 2016-01-23 00:10:40
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
● 2016-05-30 08:48:44
○ 2017-02-17 06:40:36
○ 2026-07-04 13:07:08
○A64.62.224.2532015-06-16 → 2015-06-16 · 3 obs
● 2015-06-16 19:40:20
○ 2016-01-23 00:10:40
○ 2026-07-04 13:07:08
○ 2016-01-23 00:10:40
○ 2026-07-04 13:07:08
○A74.82.63.1262016-01-23 → 2016-01-23 · 4 obs
○ 2015-06-16 19:40:20
● 2016-01-23 00:10:40
○ 2016-05-30 08:48:44
○ 2026-07-04 13:07:08
● 2016-01-23 00:10:40
○ 2016-05-30 08:48:44
○ 2026-07-04 13:07:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cn | a.dns.cn, b.dns.cn, c.dns.cn, d.dns.cn... | - |
| femo.cn | pk3.22.cn, pk4.22.cn | - |
✅ Authoritative Response
Server:39.101.68.48
NS records: pk3.22.cn, pk4.22.cn
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for femo.cn (unsigned zone)
⏱️ Timing
Total: 4323ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 5 | 154.85.60.150, 118.193.37.94... |
Analysis
Name Servers
femo.cn has two authoritative name servers — pk3.22.cn and pk4.22.cn.
femo.cn uses the same name servers as several other domains — among them duorouba.com, fotic.cn, hao120.com and two more.
Hosts with just one IP address:
pk4.22.cn resolves to 39.101.68.48.