reflexsecurity.net - dns.ninja

`reflexsecurity.net`

DNSSEC	⚠️ Not signed
NS	`ns1.turbify.com` ⚠️ Not in zone NS records
		A	20.121.230.119^{🇺🇸 Microsoft20.64.0.0/10}
NS	`ns2.turbify.com` ⚠️ Not in zone NS records
		A	134.33.240.61^{🇬🇧 Microsoft134.33.0.0/16}

`net`

	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=1785134382

Same first word

reflexsecurity.net

DNS History

11 records (2 active, 9 former)

○NSno-dyn-updates.san.yahoo.com2019-12-30 → 2019-12-30 · 4 obs

○ 2017-03-18 16:36:42
● 2019-12-30 08:59:02
○ 2026-04-09 15:04:38
○ 2026-07-27 06:58:22

○NSns1.dnsimple.com2015-06-27 → 2017-03-18 · 4 obs

● 2015-06-27 14:59:28
● 2017-03-18 16:36:42
○ 2019-12-30 08:59:02
○ 2026-07-27 06:58:22

●NSns1.turbify.com2026-04-09 → 2026-07-27 · 3 obs

○ 2019-12-30 08:59:02
● 2026-04-09 15:04:38
● 2026-07-27 06:58:22

○NSns2.dnsimple.com2015-06-27 → 2017-03-18 · 4 obs

● 2015-06-27 14:59:28
● 2017-03-18 16:36:42
○ 2019-12-30 08:59:02
○ 2026-07-27 06:58:22

●NSns2.turbify.com2026-04-09 → 2026-07-27 · 3 obs

○ 2019-12-30 08:59:02
● 2026-04-09 15:04:38
● 2026-07-27 06:58:22

○NSns3.dnsimple.com2015-06-27 → 2017-03-18 · 4 obs

● 2015-06-27 14:59:28
● 2017-03-18 16:36:42
○ 2019-12-30 08:59:02
○ 2026-07-27 06:58:22

○NSns4.dnsimple.com2015-06-27 → 2017-03-18 · 4 obs

● 2015-06-27 14:59:28
● 2017-03-18 16:36:42
○ 2019-12-30 08:59:02
○ 2026-07-27 06:58:22

○NSyns1.yahoo.com2019-12-30 → 2019-12-30 · 4 obs

○ 2017-03-18 16:36:42
● 2019-12-30 08:59:02
○ 2026-04-09 15:04:38
○ 2026-07-27 06:58:22

○NSyns2.yahoo.com2019-12-30 → 2019-12-30 · 4 obs

○ 2017-03-18 16:36:42
● 2019-12-30 08:59:02
○ 2026-04-09 15:04:38
○ 2026-07-27 06:58:22

○MXmx-biz.mail.am0.yahoodns.net2019-12-30 → 2019-12-30 · 3 obs

● 2019-12-30 08:59:02
○ 2026-04-09 15:04:38
○ 2026-07-27 06:58:22

○A67.195.197.752019-12-30 → 2019-12-30 · 3 obs

● 2019-12-30 08:59:02
○ 2026-04-09 15:04:38
○ 2026-07-27 06:58:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
reflexsecurity.net	ns1.turbify.com, ns2.turbify.com	-

✅ Authoritative Response

Server:20.121.230.119

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for reflexsecurity.net (unsigned zone)

⏱️ Timing

Total: 209ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Name Servers

reflexsecurity.net uses two name servers for its delegation: ns1.turbify.com and ns2.turbify.com.

The name server configuration of reflexsecurity.net is shared with other domains, for instance keylimedivers.com, auto1060.com, waseela.com and two others.

reflexsecurity.net has at least partial name server overlap with other domains, such as ceslegal.com, pcwappliance.com, luxushawaii.com and two others.

It is common to see these name servers used together with name servers yns1.yahoo.com and yns2.yahoo.com.

ns1.turbify.com directs to 20.121.230.119 and ns2.turbify.com directs to 134.33.240.61; each host name points to exactly one IP number.