districtup.com - robtex.com

Search for stuff

`districtup.com`

DNSSEC	⚠️ Not signed
A	18.204.183.16^{🇺🇸 Amazon}
		PTR	`ec2-18-204-183-16.compute-1.amazonaws.com`
NS	`ns1.brandnic.com`⚠️
		A	18.204.183.16^{🇺🇸 Amazon}
			PTR	`ec2-18-204-183-16.compute-1.amazonaws.com`
NS	`ns2.brandnic.com`⚠️
		A	174.129.28.221^{🇺🇸 Amazon}
			PTR	`ec2-174-129-28-221.compute-1.amazonaws.com`

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

Same first word

districtup.com

DNS History

12 records (3 active, 9 former)

●NSns1.brandnic.com2026-02-15 → 2026-02-15 · 3 obs

○ 2018-12-11 20:21:20
● 2026-02-15 12:40:12
● 2026-02-15 12:40:14

○NSns15.domaincontrol.com2018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

○NSns16.domaincontrol.com2018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

●NSns2.brandnic.com2026-02-15 → 2026-02-15 · 3 obs

○ 2018-12-11 20:21:20
● 2026-02-15 12:40:12
● 2026-02-15 12:40:14

●A18.204.183.162026-02-15 → 2026-02-15 · 3 obs

○ 2018-12-11 20:21:20
● 2026-02-15 12:40:12
● 2026-02-15 12:40:14

○A184.168.221.682018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

○A184.168.221.692018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

○A184.168.221.862018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

○A184.168.221.892018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

○A50.63.202.702018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

○A50.63.202.762018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

○A50.63.202.812018-12-11 → 2018-12-11 · 3 obs

● 2018-12-11 20:21:20
○ 2026-02-15 12:40:12
○ 2026-02-15 12:40:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
districtup.com	ns1.brandnic.com, ns2.brandnic.com	2 records

✅ Authoritative Response

Server: 174.129.28.221

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for districtup.com (unsigned zone)

⏱️ Timing

Total: 61ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`18.204.183.16`

📌 Glue Records Collected

Total: 2

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

AI analysis

districtup.com points to a single IP number: 18.204.183.16.

Other host names, for instance atlantasolutions.com, ns2.sellgy.com, www.fundrider.com, warrano.com and divoto.com share IP numbers with districtup.com.

districtup.com is delegated to two name servers: ns1.brandnic.com and ns2.brandnic.com.

districtup.com uses the same name server setup as other domains, for instance authorisy.com, datoca.com, daxaz.com, avaup.com and studyinside.com.

districtup.com shares name servers with other domains at least partially, for instance izsa.com, jewelty.com, luxedesigners.com, mottoca.com and caclu.com.

Host names with one IP number:

ns1.brandnic.com points to: 18.204.183.16.

ns2.brandnic.com points to: 174.129.28.221.