devicemanagementsystem.com - dns.ninja

`devicemanagementsystem.com`

DNSSEC	⚠️ Not signed
NS	`ns05.jpmorganchase.com` ⚠️ Not in zone NS records
		A	146.143.195.14^{🇺🇸 AS3486146.143.192.0/18}
NS	`ns06.jpmorganchase.com` ⚠️ Not in zone NS records
		A	146.143.131.14^{🇺🇸 AS3486146.143.128.0/18}
NS	`ns1.jpmorganchase.com` ⚠️ Not in zone NS records
		A	159.53.46.53^{🇺🇸 AS7743159.53.32.0/19}
			PTR	`ns1.jpmorganchase.com`
			PTR	`slmns1.paymentech.com`
NS	`ns2.jpmorganchase.com` ⚠️ Not in zone NS records
		A	146.143.67.14^{🇺🇸 AS3486146.143.64.0/18}

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

Previously MX for

devicemanagementsystem.com

Same first word

devicemanagementsystem.com

DNS History

23 records (4 active, 19 former)

○NSns.vervehosting.com2015-08-17 → 2016-03-08 · 4 obs

● 2015-08-17 03:11:20
● 2016-03-08 17:28:16
○ 2017-02-04 18:19:06
○ 2026-07-31 04:28:54

○NSns03.domaincontrol.com2018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○NSns04.domaincontrol.com2018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

●NSns05.jpmorganchase.com2026-03-15 → 2026-07-31 · 3 obs

○ 2018-12-11 16:55:00
● 2026-03-15 04:21:34
● 2026-07-31 04:28:54

●NSns06.jpmorganchase.com2026-03-15 → 2026-07-31 · 3 obs

○ 2018-12-11 16:55:00
● 2026-03-15 04:21:34
● 2026-07-31 04:28:54

●NSns1.jpmorganchase.com2026-03-15 → 2026-07-31 · 3 obs

○ 2018-12-11 16:55:00
● 2026-03-15 04:21:34
● 2026-07-31 04:28:54

○NSns1.uniregistrymarket.link2017-02-04 → 2017-02-04 · 4 obs

○ 2016-03-08 17:28:16
● 2017-02-04 18:19:06
○ 2018-12-11 16:55:00
○ 2026-07-31 04:28:54

●NSns2.jpmorganchase.com2026-03-15 → 2026-07-31 · 3 obs

○ 2018-12-11 16:55:00
● 2026-03-15 04:21:34
● 2026-07-31 04:28:54

○NSns2.uniregistrymarket.link2017-02-04 → 2017-02-04 · 4 obs

○ 2016-03-08 17:28:16
● 2017-02-04 18:19:06
○ 2018-12-11 16:55:00
○ 2026-07-31 04:28:54

○NSns2.vervehosting.com2015-08-17 → 2016-03-08 · 4 obs

● 2015-08-17 03:11:20
● 2016-03-08 17:28:16
○ 2017-02-04 18:19:06
○ 2026-07-31 04:28:54

○NSns3.vervehosting.com2015-08-17 → 2016-03-08 · 4 obs

● 2015-08-17 03:11:20
● 2016-03-08 17:28:16
○ 2017-02-04 18:19:06
○ 2026-07-31 04:28:54

○MXdevicemanagementsystem.com2015-08-17 → 2016-03-08 · 4 obs

● 2015-08-17 03:11:20
● 2016-03-08 17:28:16
○ 2017-02-04 18:19:06
○ 2026-07-31 04:28:54

○A184.168.221.452018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A184.168.221.472018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A184.168.221.492018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A184.168.221.512018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A209.212.146.122015-08-17 → 2016-03-08 · 4 obs

● 2015-08-17 03:11:20
● 2016-03-08 17:28:16
○ 2017-02-04 18:19:06
○ 2026-07-31 04:28:54

○A50.63.202.352018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A50.63.202.382018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A50.63.202.452018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A50.63.202.462018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A50.63.202.492018-12-11 → 2018-12-11 · 4 obs

○ 2017-02-04 18:19:06
● 2018-12-11 16:55:00
○ 2026-03-15 04:21:34
○ 2026-07-31 04:28:54

○A69.172.201.1532017-02-04 → 2017-02-04 · 4 obs

○ 2016-03-08 17:28:16
● 2017-02-04 18:19:06
○ 2018-12-11 16:55:00
○ 2026-07-31 04:28:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, m.gtld-servers.net, h.gtld-servers.net, k.gtld-servers.net...	-
devicemanagementsystem.com	ns1.jpmorganchase.com, ns2.jpmorganchase.com, ns05.jpmorganchase.com, ns06.jpmorganchase.com	4 records

✅ Authoritative Response

Server:159.53.46.53

NS records: ns1.jpmorganchase.com, ns2.jpmorganchase.com, ns05.jpmorganchase.com, ns06.jpmorganchase.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for devicemanagementsystem.com (unsigned zone)

⏱️ Timing

Total: 3140ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.jpmorganchase.com, ns06.jpmorganchase.com...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.jpmorganchase.com hostmaster.jpmchas`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.jpmorganchase.com, ns2.jpmorganchase.com, ns05.jpmorganchase.com...)

Analysis

Name Servers

devicemanagementsystem.com has four authoritative name servers: ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com and ns2.jpmorganchase.com.

devicemanagementsystem.com shares at least some of its name servers with other domains, including ratescenter.com, servicechase-paymentech.com, chaseedisclosures.com and two others.

These name servers are frequently seen alongside ns0037.secondary.cloudflare.com, ns0246.secondary.cloudflare.com, ns0087.secondary.cloudflare.com and 3 other name servers.

ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com and ns2.jpmorganchase.com each resolve to one IP address: ns05.jpmorganchase.com resolves to 146.143.195.14, ns06.jpmorganchase.com resolves to 146.143.131.14, ns1.jpmorganchase.com resolves to 159.53.46.53 and ns2.jpmorganchase.com resolves to 146.143.67.14.