`innotecsecurity.com`

DNSSEC	⚠️ Not signed
A	18.101.30.184^{🇪🇸 Amazon18.100.0.0/15 EC2 ZAZ Prefix}
		PTR	`ec2-18-101-30-184.eu-south-2.compute.amazonaws.com`
A	18.101.50.199^{🇪🇸 Amazon18.100.0.0/15 EC2 ZAZ Prefix}
NS	`amrns1501.accenture.com` ⭐
		A	170.252.248.5^{🇺🇸 ANSER_ADVISORY170.252.248.0/24}
			PTR	`amrns1501.accenture.com`
NS	`apans3501.accenture.com`
		A	170.252.160.140^{🇵🇭 ANSER_ADVISORY170.252.160.0/24}
			PTR	`apans3501.accenture.com`
NS	`cfans1001.accenture.com`
		A	162.159.8.127^{Cloudflare162.159.8.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`cfans1002.accenture.com`
		A	162.159.9.58^{Cloudflare162.159.9.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`emens3501.accenture.com`
		A	170.252.72.92^{🇪🇸 ANSER_ADVISORY170.252.72.0/21 Accenture Route Object}
			PTR	`emens3501.accenture.com`
TXT	`v=spf1-all`
SOA	`amrns1501.accenture.com`dnsadmin@accenture.com serial=6170

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

Same first word

innotecsecurity.es

innotecsecurity.io

innotecsecurity.com

DNS History

11 records (7 active, 4 former)

●NSamrns1501.accenture.com2026-02-23 → 2026-03-23 · 3 obs

○ 2018-06-18 11:13:30
● 2026-02-23 10:57:32
● 2026-03-23 23:05:14

●NSapans3501.accenture.com2026-02-23 → 2026-03-23 · 3 obs

○ 2018-06-18 11:13:30
● 2026-02-23 10:57:32
● 2026-03-23 23:05:14

●NScfans1001.accenture.com2026-02-23 → 2026-03-23 · 3 obs

○ 2018-06-18 11:13:30
● 2026-02-23 10:57:32
● 2026-03-23 23:05:14

●NScfans1002.accenture.com2026-02-23 → 2026-03-23 · 3 obs

○ 2018-06-18 11:13:30
● 2026-02-23 10:57:32
● 2026-03-23 23:05:14

●NSemens3501.accenture.com2026-02-23 → 2026-03-23 · 3 obs

○ 2018-06-18 11:13:30
● 2026-02-23 10:57:32
● 2026-03-23 23:05:14

○NSns13.domaincontrol.com2016-12-16 → 2018-06-18 · 4 obs

● 2016-12-16 18:04:50
● 2018-06-18 11:13:30
○ 2026-02-23 10:57:32
○ 2026-03-23 23:05:14

○NSns14.domaincontrol.com2016-12-16 → 2018-06-18 · 4 obs

● 2016-12-16 18:04:50
● 2018-06-18 11:13:30
○ 2026-02-23 10:57:32
○ 2026-03-23 23:05:14

○MXmail.innotecsecurity.com2016-12-16 → 2018-06-18 · 4 obs

● 2016-12-16 18:04:50
● 2018-06-18 11:13:30
○ 2026-02-23 10:57:32
○ 2026-03-23 23:05:14

●A18.101.30.1842026-02-23 → 2026-03-23 · 3 obs

○ 2018-06-18 11:13:30
● 2026-02-23 10:57:32
● 2026-03-23 23:05:14

●A18.101.50.1992026-02-23 → 2026-03-23 · 3 obs

○ 2018-06-18 11:13:30
● 2026-02-23 10:57:32
● 2026-03-23 23:05:14

○A192.186.213.352016-12-16 → 2018-06-18 · 4 obs

● 2016-12-16 18:04:50
● 2018-06-18 11:13:30
○ 2026-02-23 10:57:32
○ 2026-03-23 23:05:14

🔍 DNS Trace

Analysis

IP Addresses

innotecsecurity.com resolves to two IP numbers: 18.101.30.184 and 18.101.50.199.

Other host names, for instance ec2-18-101-30-184.eu-south-2.compute.amazonaws.com, innotecsecurity.es, ec2-18-101-50-199.eu-south-2.compute.amazonaws.com, innotecsecurity.io and innot.ec share IP numbers with innotecsecurity.com.

Name Servers

innotecsecurity.com delegates to five name servers: amrns1501.accenture.com, apans3501.accenture.com, cfans1001.accenture.com, cfans1002.accenture.com and emens3501.accenture.com.

innotecsecurity.com shares some name servers with other domains, for example froneribpo.com.br, accenrure.com, cloud-ocsp.com, appspro-me.com and accen-ture.com.

These name servers are commonly used together with emens1901.accenture.com and amrns1501accenture.com.

Host names with one IP number:

- amrns1501.accenture.com points to: 170.252.248.5

- apans3501.accenture.com points to: 170.252.160.140

- cfans1001.accenture.com points to: 162.159.8.127

- cfans1002.accenture.com points to: 162.159.9.58

- emens3501.accenture.com points to: 170.252.72.92

innotecsecurity.com - robtex.com