wanfly.com - dns.ninja

wanfly.com

DNSSEC⚠️ Not signed
A52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix
PTRec2-52-20-84-62.compute-1.amazonaws.com
NSns1.atom.com ⭐
A44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix
PTRec2-44-219-81-145.compute-1.amazonaws.com
NSns2.atom.com
A50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix
PTRec2-50-19-240-86.compute-1.amazonaws.com
SOAns1.atom.comhostmaster@wanfly.com 2025-11-11 #1

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1786205134

Same first word

wanfly.com

Similar names

flywan.net
flywan.com

DNS History

20 records (3 active, 17 former)

20162017201820192020202120222023202420252026NSns1.atom.comns2.atom.comlaunch1.spaceship.netlaunch2.spaceship.netns1.22.cnns1.afternic.comns2.22.cnns2.afternic.comns3.22.cnns4.22.cnA52.20.84.6213.248.169.4844.232.173.24952.40.42.11364.62.171.13564.62.224.25376.223.54.146CNAME51owner.comfw1.22.cnpark.jinmi.com
○NSlaunch1.spaceship.net2026-03-12 → 2026-08-08 · 2 obs
○ 2026-03-12 00:36:26
○ 2026-08-08 16:28:40
○NSlaunch2.spaceship.net2026-03-12 → 2026-08-08 · 2 obs
○ 2026-03-12 00:36:26
○ 2026-08-08 16:28:40
○NSns1.22.cn2016-01-02 → 2016-09-21 · 4 obs
● 2016-01-02 09:08:32
● 2016-09-21 23:05:56
○ 2017-09-15 04:45:16
○ 2026-08-08 16:28:40
○NSns1.afternic.com2026-03-12 → 2026-07-19 · 7 obs
○ 2017-09-15 04:45:16
● 2026-03-12 00:36:26
● 2026-03-15 14:53:56
○ 2026-04-15 07:17:06
● 2026-07-19 10:34:36
○ 2026-08-08 16:28:38
○ 2026-08-08 16:28:40
●NSns1.atom.com2026-04-15 → 2026-08-08 · 5 obs
○ 2026-03-15 14:53:56
● 2026-04-15 07:17:06
○ 2026-07-19 10:34:36
● 2026-08-08 16:28:38
● 2026-08-08 16:28:40
○NSns2.22.cn2016-01-02 → 2016-09-21 · 4 obs
● 2016-01-02 09:08:32
● 2016-09-21 23:05:56
○ 2017-09-15 04:45:16
○ 2026-08-08 16:28:40
○NSns2.afternic.com2026-03-12 → 2026-07-19 · 7 obs
○ 2017-09-15 04:45:16
● 2026-03-12 00:36:26
● 2026-03-15 14:53:56
○ 2026-04-15 07:17:06
● 2026-07-19 10:34:36
○ 2026-08-08 16:28:38
○ 2026-08-08 16:28:40
●NSns2.atom.com2026-04-15 → 2026-08-08 · 5 obs
○ 2026-03-15 14:53:56
● 2026-04-15 07:17:06
○ 2026-07-19 10:34:36
● 2026-08-08 16:28:38
● 2026-08-08 16:28:40
○NSns3.22.cn2016-01-02 → 2016-09-21 · 4 obs
● 2016-01-02 09:08:32
● 2016-09-21 23:05:56
○ 2017-09-15 04:45:16
○ 2026-08-08 16:28:40
○NSns4.22.cn2016-01-02 → 2016-09-21 · 4 obs
● 2016-01-02 09:08:32
● 2016-09-21 23:05:56
○ 2017-09-15 04:45:16
○ 2026-08-08 16:28:40
○A13.248.169.482026-03-12 → 2026-07-19 · 7 obs
○ 2017-09-15 04:45:16
● 2026-03-12 00:36:26
● 2026-03-15 14:53:56
○ 2026-04-15 07:17:06
● 2026-07-19 10:34:36
○ 2026-08-08 16:28:38
○ 2026-08-08 16:28:40
○A44.232.173.2492026-03-12 → 2026-08-08 · 2 obs
○ 2026-03-12 00:36:26
○ 2026-08-08 16:28:40
●A52.20.84.622026-04-15 → 2026-08-08 · 5 obs
○ 2026-03-15 14:53:56
● 2026-04-15 07:17:06
○ 2026-07-19 10:34:36
● 2026-08-08 16:28:38
● 2026-08-08 16:28:40
○A52.40.42.1132026-03-12 → 2026-08-08 · 2 obs
○ 2026-03-12 00:36:26
○ 2026-08-08 16:28:40
○A64.62.171.1352016-01-02 → 2016-01-02 · 4 obs
○ 2015-10-28 06:12:18
● 2016-01-02 09:08:32
○ 2017-09-15 04:45:16
○ 2026-08-08 16:28:40
○A64.62.224.2532015-06-02 → 2015-10-28 · 4 obs
● 2015-06-02 04:50:12
● 2015-10-28 06:12:18
○ 2016-01-02 09:08:32
○ 2026-08-08 16:28:40
○A76.223.54.1462026-03-12 → 2026-07-19 · 7 obs
○ 2017-09-15 04:45:16
● 2026-03-12 00:36:26
● 2026-03-15 14:53:56
○ 2026-04-15 07:17:06
● 2026-07-19 10:34:36
○ 2026-08-08 16:28:38
○ 2026-08-08 16:28:40
○CNAME51owner.com2016-09-21 → 2016-09-21 · 4 obs
○ 2016-01-02 09:08:32
● 2016-09-21 23:05:56
○ 2017-09-15 04:45:16
○ 2026-08-08 16:28:40
○CNAMEfw1.22.cn2016-01-02 → 2016-01-02 · 3 obs
● 2016-01-02 09:08:32
○ 2016-09-21 23:05:56
○ 2026-08-08 16:28:40
○CNAMEpark.jinmi.com2017-09-15 → 2017-09-15 · 4 obs
○ 2016-09-21 23:05:56
● 2017-09-15 04:45:16
○ 2026-03-12 00:36:26
○ 2026-08-08 16:28:40

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
wanfly.comns1.atom.com, ns2.atom.com2 records

✅ Authoritative Response

Server:44.219.81.145

NS records: ns1.atom.com, ns2.atom.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for wanfly.com (unsigned zone)

⏱️ Timing

Total: 3046ms | Queries: -

📄 Records

TypeCountSample Data
A152.20.84.62
NS2ns2.atom.com, ns1.atom.com
SOA1ns1.atom.com hostmaster.wanfly.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)

Analysis

IP Addresses

wanfly.com directs to one IP number, which is 52.20.84.62.

Among the host names that share IP numbers with wanfly.com are gamenifty.com, mediarove.com, logixwave.com and two others.

Name Servers

The NS records for wanfly.com delegate to ns1.atom.com and ns2.atom.com.

wanfly.com has the same name server delegation as a number of other domains, such as chapeltalk.com, foodema.com, tribeid.com and two more.

wanfly.com at least partially shares name servers with other domains, including takfa.com, perafox.com, maigy.com and joygrass.com.

ns1.atom.com and ns2.atom.com each resolve to one IP number: ns1.atom.com points to 44.219.81.145 and ns2.atom.com points to 50.19.240.86.