flexns.com - dns.ninja

`flexns.com`

DNSSEC	⚠️ Not signed
NS	`a.m1ns.com` ⭐
		A	2a0d:2900:a::^{🇺🇸 MISAKA-ANYCAST2a0d:2900:a::/48 Misaka Network, Inc.}
			PTR	`a.m1ns.com`
		A	188.244.98.0^{🇺🇸 MISAKA-ANYCAST188.244.98.0/24 Misaka.io Customer Infrastructure in Hong Kong}
			PTR	`a.m1ns.com`
NS	`b.m1ns.net`
		A	2a0d:2900:b::1^{🇺🇸 MISAKA-ANYCAST2a0d:2900:b::/48 Misaka Network, Inc.}
			PTR	`b.m1ns.net`
		A	188.244.99.3^{🇺🇸 MISAKA-ANYCAST188.244.99.0/24 Misaka.io}
			PTR	`b.m1ns.net`
NS	`c.m1ns.org`
		A	2a0d:2900:c::2^{🇺🇸 MISAKA-ANYCAST2a0d:2900:c::/48 Misaka Network, Inc.}
			PTR	`c.m1ns.org`
		A	188.244.98.7^{🇺🇸 MISAKA-ANYCAST188.244.98.0/24 Misaka.io Customer Infrastructure in Hong Kong}
			PTR	`c.m1ns.org`
NS	`d.m1ns.xyz`
		A	2a0d:2900:d::3^{🇺🇸 MISAKA-ANYCAST2a0d:2900:d::/48 Misaka Network, Inc.}
			PTR	`d.m1ns.xyz`
		A	188.244.99.10^{🇺🇸 MISAKA-ANYCAST188.244.99.0/24 Misaka.io}
			PTR	`d.m1ns.xyz`
NS	`e.m1ns.one` ⚠️ Not in parent delegation
		A	2a0d:2900:e::4^{🇺🇸 MISAKA-ANYCAST2a0d:2900:e::/48 Misaka Network, Inc.}
			PTR	`e.m1ns.one`
		A	188.244.98.14^{🇺🇸 MISAKA-ANYCAST188.244.98.0/24 Misaka.io Customer Infrastructure in Hong Kong}
			PTR	`e.m1ns.one`
NS	`f.m1ns.moe` ⚠️ Not in parent delegation
		A	2a0d:2900:f::5^{🇺🇸 MISAKA-ANYCAST2a0d:2900:f::/48 Misaka Network, Inc.}
			PTR	`f.m1ns.moe`
		A	188.244.99.17^{🇺🇸 MISAKA-ANYCAST188.244.99.0/24 Misaka.io}
			PTR	`f.m1ns.moe`
SOA	`a.m1ns.com`dnsops@misaka.io 2021-12-31 #10

`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.net`nstld@verisign-grs.com serial=1785420062

Same first word

flexns.com

flexns.de

Similar names

fxlens.com

lensfx.com

flexsn.com

nsflex.com

DNS History

16 records (6 active, 10 former)

●NSa.m1ns.com2026-03-28 → 2026-07-30 · 3 obs

○ 2018-10-01 14:22:52
● 2026-03-28 22:24:04
● 2026-07-30 14:31:10

○NSans1.active24.com2015-08-14 → 2015-08-14 · 3 obs

● 2015-08-14 06:18:26
○ 2015-12-09 22:15:36
○ 2026-07-30 14:31:10

○NSans2.active24.com2015-08-14 → 2015-08-14 · 3 obs

● 2015-08-14 06:18:26
○ 2015-12-09 22:15:36
○ 2026-07-30 14:31:10

○NSans3.active24.com2015-08-14 → 2015-08-14 · 3 obs

● 2015-08-14 06:18:26
○ 2015-12-09 22:15:36
○ 2026-07-30 14:31:10

●NSb.m1ns.net2026-03-28 → 2026-07-30 · 3 obs

○ 2018-10-01 14:22:52
● 2026-03-28 22:24:04
● 2026-07-30 14:31:10

●NSc.m1ns.org2026-03-28 → 2026-07-30 · 3 obs

○ 2018-10-01 14:22:52
● 2026-03-28 22:24:04
● 2026-07-30 14:31:10

●NSd.m1ns.xyz2026-03-28 → 2026-07-30 · 3 obs

○ 2018-10-01 14:22:52
● 2026-03-28 22:24:04
● 2026-07-30 14:31:10

○NSdns1.name-services.com2016-04-03 → 2018-10-01 · 5 obs

○ 2015-12-09 22:15:36
● 2016-04-03 12:10:14
● 2018-10-01 14:22:52
○ 2026-03-28 22:24:04
○ 2026-07-30 14:31:10

○NSdns2.name-services.com2016-04-03 → 2018-10-01 · 5 obs

○ 2015-12-09 22:15:36
● 2016-04-03 12:10:14
● 2018-10-01 14:22:52
○ 2026-03-28 22:24:04
○ 2026-07-30 14:31:10

○NSdns3.name-services.com2016-04-03 → 2018-10-01 · 5 obs

○ 2015-12-09 22:15:36
● 2016-04-03 12:10:14
● 2018-10-01 14:22:52
○ 2026-03-28 22:24:04
○ 2026-07-30 14:31:10

○NSdns4.name-services.com2016-04-03 → 2018-10-01 · 5 obs

○ 2015-12-09 22:15:36
● 2016-04-03 12:10:14
● 2018-10-01 14:22:52
○ 2026-03-28 22:24:04
○ 2026-07-30 14:31:10

○NSdns5.name-services.com2016-04-03 → 2018-10-01 · 5 obs

○ 2015-12-09 22:15:36
● 2016-04-03 12:10:14
● 2018-10-01 14:22:52
○ 2026-03-28 22:24:04
○ 2026-07-30 14:31:10

●NSe.m1ns.one2026-03-28 → 2026-07-30 · 3 obs

○ 2018-10-01 14:22:52
● 2026-03-28 22:24:04
● 2026-07-30 14:31:10

●NSf.m1ns.moe2026-03-28 → 2026-07-30 · 3 obs

○ 2018-10-01 14:22:52
● 2026-03-28 22:24:04
● 2026-07-30 14:31:10

○A213.188.129.1832015-08-14 → 2015-08-14 · 3 obs

● 2015-08-14 06:18:26
○ 2015-12-09 22:15:36
○ 2026-07-30 14:31:10

○A98.124.204.162016-04-03 → 2018-10-01 · 5 obs

○ 2015-12-09 22:15:36
● 2016-04-03 12:10:14
● 2018-10-01 14:22:52
○ 2026-03-28 22:24:04
○ 2026-07-30 14:31:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
flexns.com	a.m1ns.com, b.m1ns.net, c.m1ns.org, d.m1ns.xyz	2 records

✅ Authoritative Response

Server:188.244.98.0

NS records: a.m1ns.com, b.m1ns.net, c.m1ns.org, d.m1ns.xyz

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for flexns.com (unsigned zone)

⏱️ Timing

Total: 270ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	6	`a.m1ns.com, b.m1ns.net...`
SOA	1	`a.m1ns.com dnsops.misaka.io`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (a.m1ns.com, a.m1ns.com)

Analysis

Name Servers

flexns.com delegates authority to 6 name servers: a.m1ns.com, f.m1ns.moe, b.m1ns.net plus 3 other.

The name servers of flexns.com overlap at least partially with those of other domains — among them 58.203.103.in-addr.arpa, 72.189.185.in-addr.arpa, orztech.top and two more.

These name servers commonly appear in delegations together with e.m1ns.one, c.m1ns.org, d.m1ns.xyz and 6 other.

Host names that have two IP addresses:

a.m1ns.com directs traffic to 188.244.98.0 and 2a0d:2900:a::.

f.m1ns.moe directs traffic to 188.244.99.17 and 2a0d:2900:f::5.

b.m1ns.net directs traffic to 188.244.99.3 and 2a0d:2900:b::1.

e.m1ns.one directs traffic to 188.244.98.14 and 2a0d:2900:e::4.

c.m1ns.org directs traffic to 188.244.98.7 and 2a0d:2900:c::2.

d.m1ns.xyz directs traffic to 188.244.99.10 and 2a0d:2900:d::3.