me2c.top - robtex.com
me2c.top
| CNAME | g1ada11.tz.iflvopx.net | ||||||
| DNSSEC | ⚠️ Not signed | ||||||
| A | 154.218.0.14🇭🇰 HKMTC-AS-AP154.218.0.0/24 Hong Kong megalayer | ||||||
| A | 154.218.0.57🇭🇰 HKMTC-AS-AP154.218.0.0/24 Hong Kong megalayer | ||||||
| A | 154.218.0.95🇭🇰 HKMTC-AS-AP154.218.0.0/24 Hong Kong megalayer | ||||||
top
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.zdnscloud.com ⭐ | ||||||
| NS | a.zdnscloud.cn | ||||||
| NS | b.zdnscloud.cn | ||||||
| NS | c.zdnscloud.com | ||||||
| NS | d.zdnscloud.com | ||||||
| NS | e.zdnscloud.cn | ||||||
| NS | f.zdnscloud.cn | ||||||
| NS | i.zdnscloud.cn | ||||||
| NS | j.zdnscloud.com | ||||||
| TXT | 2026-08-14_07:50:01 | ||||||
| SOA | a.zdnscloud.comtd_dns_gtld@knet.cn serial=1396753744 | ||||||
Same first word
Similar names
DNS History
3 records (3 active, 0 former)
●NSns1.spixiv.com2026-05-01 → 2026-08-14 · 2 obs
● 2026-05-01 08:22:42
● 2026-08-14 00:13:54
● 2026-08-14 00:13:54
●NSns2.spixiv.com2026-05-01 → 2026-08-14 · 2 obs
● 2026-05-01 08:22:42
● 2026-08-14 00:13:54
● 2026-08-14 00:13:54
●CNAMEg1ada11.tz.iflvopx.net2026-05-01 → 2026-08-14 · 2 obs
● 2026-05-01 08:22:42
● 2026-08-14 00:13:54
● 2026-08-14 00:13:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| top | a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com, d.zdnscloud.com... | - |
| me2c.top | ns1.spixiv.com, ns2.spixiv.com | - |
✅ Authoritative Response
Server:99.83.220.212
NS records: ns1.spixiv.com, ns2.spixiv.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for me2c.top (unsigned zone)
⏱️ Timing
Total: 674ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | g1ada11.tz.iflvopx.net |
| SOA | 1 | ns1.spixiv.com hostmaster.spixiv.com |
Analysis
IP Addresses
me2c.top maps to three IP numbers — 154.218.0.14, 154.218.0.57 and 154.218.0.95.
g1ada11.tz.iflvopx.net, for instance, is one of the other host names sharing IP numbers with me2c.top.