ddosprotected.com - dns.ninja

`ddosprotected.com`

DNSSEC	⚠️ Not signed
NS	`ns1.level3.net` ⭐ ⚠️ Not in parent delegation
		A	209.244.0.1^{🇺🇸 AS3356209.244.0.0/14}
			PTR	`ns1.level3.net`
NS	`ns1.l3.net` ⚠️ Not in zone NS records
		A	209.244.0.1^{🇺🇸 AS3356209.244.0.0/14}
			PTR	`ns1.level3.net`
NS	`ns2.l3.net` ⚠️ Not in zone NS records
		A	209.244.0.2^{🇺🇸 AS3356209.244.0.0/14}
			PTR	`ns2.level3.net`
NS	`ns2.level3.net` ⚠️ Not in parent delegation
		A	209.244.0.2^{🇺🇸 AS3356209.244.0.0/14}
			PTR	`ns2.level3.net`
SOA	`ns1.Level3.net`dns@level3.net 2025-05-09 #1

`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=1786534794

Same first word

ddosprotected.org

ddosprotected.com

DNS History

7 records (4 active, 3 former)

○NSns1.ddosprotected.com2015-08-26 → 2016-01-15 · 4 obs

● 2015-08-26 04:55:14
● 2016-01-15 19:45:38
○ 2026-03-16 23:04:14
○ 2026-08-12 11:46:20

●NSns1.l3.net2026-03-16 → 2026-08-12 · 3 obs

○ 2016-01-15 19:45:38
● 2026-03-16 23:04:14
● 2026-08-12 11:46:20

●NSns1.level3.net2026-03-16 → 2026-08-12 · 6 obs

○ 2016-01-15 19:45:38
● 2026-03-16 23:04:14
● 2026-04-13 09:16:40
○ 2026-04-13 15:47:20
● 2026-04-13 17:42:12
● 2026-08-12 11:46:20

○NSns2.ddosprotected.com2015-08-26 → 2016-01-15 · 4 obs

● 2015-08-26 04:55:14
● 2016-01-15 19:45:38
○ 2026-03-16 23:04:14
○ 2026-08-12 11:46:20

●NSns2.l3.net2026-03-16 → 2026-08-12 · 3 obs

○ 2016-01-15 19:45:38
● 2026-03-16 23:04:14
● 2026-08-12 11:46:20

●NSns2.level3.net2026-03-16 → 2026-08-12 · 8 obs

○ 2016-01-15 19:45:38
● 2026-03-16 23:04:14
○ 2026-04-13 06:49:38
● 2026-04-13 09:16:40
○ 2026-04-13 15:47:20
○ 2026-04-13 17:42:12
● 2026-05-09 12:20:24
● 2026-08-12 11:46:20

○A208.64.126.302015-08-26 → 2016-01-15 · 4 obs

● 2015-08-26 04:55:14
● 2016-01-15 19:45:38
○ 2026-03-16 23:04:14
○ 2026-08-12 11:46:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ddosprotected.com	ns1.l3.net, ns2.l3.net	-

✅ Authoritative Response

Server:209.244.0.2

NS records: ns1.l3.net, ns2.l3.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ddosprotected.com (unsigned zone)

⏱️ Timing

Total: 843ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns2.Level3.net, ns1.Level3.net`
SOA	1	`ns1.Level3.net dns.level3.net`

Analysis

Name Servers

The NS records for ddosprotected.com point to four name servers: ns1.l3.net, ns2.l3.net, ns1.level3.net and ns2.level3.net.

The name servers of ddosprotected.com overlap at least partially with those of other domains — among them level3.email, 154.64.in-addr.arpa, pittsburgh3.level3.net and two more.

These name servers commonly appear alongside the name servers dnsmgr2.level3.net and iresolver1.mgmt.level3.net.

Each of the host names ns1.l3.net, ns2.l3.net, ns1.level3.net and ns2.level3.net has one IP address: ns1.l3.net resolves to 209.244.0.1, ns2.l3.net resolves to 209.244.0.2, ns1.level3.net resolves to 209.244.0.1 and ns2.level3.net resolves to 209.244.0.2.

Both ns1.l3.net and ns1.level3.net resolve to 209.244.0.1 IP addresses each.

Both ns2.l3.net and ns2.level3.net resolve to 209.244.0.2 IP addresses each.