f2mede.top - robtex.com
f2mede.top
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-07-18_07:05:01 | ||||||
| SOA | a.zdnscloud.comtd_dns_gtld@knet.cn serial=1396488663 | ||||||
Same first word
f2mede.top |
DNS History
11 records (3 active, 8 former)
○NSd.ns.arvancdn.ir2026-03-21 → 2026-03-26 · 4 obs
● 2026-03-26 22:54:22
○ 2026-05-22 04:41:02
○ 2026-07-17 23:24:40
●NSduke.ns.cloudflare.com2026-05-22 → 2026-07-17 · 3 obs
● 2026-05-22 04:41:02
● 2026-07-17 23:24:40
○NSp.ns.globalcdntech.com2026-03-21 → 2026-03-26 · 4 obs
● 2026-03-26 22:54:22
○ 2026-05-22 04:41:02
○ 2026-07-17 23:24:40
●NSsneh.ns.cloudflare.com2026-05-22 → 2026-07-17 · 3 obs
● 2026-05-22 04:41:02
● 2026-07-17 23:24:40
○NSw.ns.globalcdntech.com2026-03-21 → 2026-03-26 · 4 obs
● 2026-03-26 22:54:22
○ 2026-05-22 04:41:02
○ 2026-07-17 23:24:40
○NSy.ns.arvancdn.ir2026-03-21 → 2026-03-26 · 4 obs
● 2026-03-26 22:54:22
○ 2026-05-22 04:41:02
○ 2026-07-17 23:24:40
○A185.143.233.2352026-03-21 → 2026-03-26 · 7 obs
● 2026-03-22 23:02:14
○ 2026-03-25 20:40:34
● 2026-03-26 13:31:44
● 2026-03-26 22:54:22
○ 2026-05-22 04:41:02
○ 2026-07-17 23:24:40
○A185.143.233.2372026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 20:40:34
○ 2026-03-26 13:31:44
○ 2026-07-17 23:24:40
○A185.143.234.2352026-03-21 → 2026-03-26 · 7 obs
● 2026-03-22 23:02:14
○ 2026-03-25 20:40:34
● 2026-03-26 13:31:44
● 2026-03-26 22:54:22
○ 2026-05-22 04:41:02
○ 2026-07-17 23:24:40
○A185.143.234.2372026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 20:40:34
○ 2026-03-26 13:31:44
○ 2026-07-17 23:24:40
●A79.175.176.1002026-05-22 → 2026-07-17 · 3 obs
● 2026-05-22 04:41:02
● 2026-07-17 23:24:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| top | a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com, d.zdnscloud.com... | 9 records |
| f2mede.top | duke.ns.cloudflare.com, sneh.ns.cloudflare.com | - |
✅ Authoritative Response
Server:173.245.59.110
NS records: duke.ns.cloudflare.com, sneh.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for f2mede.top (unsigned zone)
⏱️ Timing
Total: 374ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 79.175.176.100 |
| NS | 2 | duke.ns.cloudflare.com, sneh.ns.cloudflare.com |
| SOA | 1 | duke.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 9
Out-of-bailiwick: 9 (a.zdnscloud.cn, b.zdnscloud.cn, c.zdnscloud.com...)
Analysis
IP Addresses
f2mede.top points to a single IP number: 79.175.176.100.
Additional host names — roshdafza.top, zarvaz.top, oldtowns.top and two others — share IP numbers with f2mede.top.
Name Servers
f2mede.top is delegated to two name servers: duke.ns.cloudflare.com and sneh.ns.cloudflare.com.
f2mede.top shares its name server setup with other domains, including myf2me.top, tejaratban.top, myf2mx.top and two others.
At least some of f2mede.top's name servers are shared with other domains, for example tandongphuc.vn, kastatotosuka.com, mytemyweb.com and two more.
These name servers tend to be deployed in combination with the name servers stan.ns.cloudflare.com and martha.ns.cloudflare.com.
Host names with 6 IP numbers:
duke.ns.cloudflare.com resolves to 108.162.193.110, 172.64.33.110, 173.245.59.110 and 3 other IP addresses.
sneh.ns.cloudflare.com resolves to 108.162.194.162, 162.159.38.162, 172.64.34.162 and 3 other IP addresses.