execution.in - dns.ninja

`execution.in`

DNSSEC	⚠️ Not signed
A	54.195.35.206^{🇮🇪 Amazon54.195.0.0/16 EC2 DUB prefix}
		PTR	`ec2-54-195-35-206.eu-west-1.compute.amazonaws.com`
NS	`ns1.execution.in` ⭐
NS	`ns1.daaz.org`
		A	54.154.209.236^{🇮🇪 Amazon54.154.0.0/16 EC2 DUB prefix}
			PTR	`ec2-54-154-209-236.eu-west-1.compute.amazonaws.com`
NS	`ns2.daaz.org`
		A	54.72.75.63^{🇮🇪 Amazon54.72.0.0/16 EC2 DUB prefix}
			PTR	`ec2-54-72-75-63.eu-west-1.compute.amazonaws.com`
TXT	`v=spf1 -all`
SOA	`ns1.execution.in`hostmaster@execution.in 2025-09-19 #1

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns1.registry.in` ⚠️ Not in parent delegation
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	NS	`ns2.registry.in` ⚠️ Not in parent delegation
	NS	`ns3.registry.in` ⚠️ Not in parent delegation
	NS	`ns4.registry.in` ⚠️ Not in parent delegation
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1780789257

Same first word

execution.me

execution.eu

execution.com.br

execution.us

execution.in

execution.dk

execution.cn

execution.biz

execution.partners

execution.ru

execution.pro

execution.de

execution.net

execution.com

execution.be

execution.io

execution.su

execution.management

DNS History

20 records (4 active, 16 former)

●NSns1.daaz.org2026-03-17 → 2026-06-07 · 3 obs

○ 2018-09-11 18:12:46
● 2026-03-17 18:14:16
● 2026-06-07 00:06:18

●NSns1.execution.in2026-03-17 → 2026-06-07 · 3 obs

○ 2018-09-11 18:12:46
● 2026-03-17 18:14:16
● 2026-06-07 00:06:18

○NSns1.mitsu.in2016-02-09 → 2016-05-09 · 4 obs

● 2016-02-09 11:51:56
● 2016-05-09 05:38:50
○ 2017-01-31 10:06:40
○ 2026-06-07 00:06:18

○NSns1.sedoparking.com2018-09-11 → 2018-09-11 · 4 obs

○ 2017-01-31 10:06:40
● 2018-09-11 18:12:46
○ 2026-03-17 18:14:16
○ 2026-06-07 00:06:18

○NSns1381.ztomy.com2017-01-31 → 2017-01-31 · 4 obs

○ 2016-05-09 05:38:50
● 2017-01-31 10:06:40
○ 2018-09-11 18:12:46
○ 2026-06-07 00:06:18

●NSns2.daaz.org2026-03-17 → 2026-06-07 · 3 obs

○ 2018-09-11 18:12:46
● 2026-03-17 18:14:16
● 2026-06-07 00:06:18

○NSns2.mitsu.in2016-02-09 → 2016-05-09 · 4 obs

● 2016-02-09 11:51:56
● 2016-05-09 05:38:50
○ 2017-01-31 10:06:40
○ 2026-06-07 00:06:18

○NSns2.sedoparking.com2018-09-11 → 2018-09-11 · 4 obs

○ 2017-01-31 10:06:40
● 2018-09-11 18:12:46
○ 2026-03-17 18:14:16
○ 2026-06-07 00:06:18

○NSns2381.ztomy.com2017-01-31 → 2017-01-31 · 4 obs

○ 2016-05-09 05:38:50
● 2017-01-31 10:06:40
○ 2018-09-11 18:12:46
○ 2026-06-07 00:06:18

○NSns3.mitsu.in2016-02-09 → 2016-05-09 · 4 obs

● 2016-02-09 11:51:56
● 2016-05-09 05:38:50
○ 2017-01-31 10:06:40
○ 2026-06-07 00:06:18

○NSns4.mitsu.in2016-02-09 → 2016-05-09 · 4 obs

● 2016-02-09 11:51:56
● 2016-05-09 05:38:50
○ 2017-01-31 10:06:40
○ 2026-06-07 00:06:18

○MXlocalhost2018-09-11 → 2018-09-11 · 4 obs

○ 2017-01-31 10:06:40
● 2018-09-11 18:12:46
○ 2026-03-17 18:14:16
○ 2026-06-07 00:06:18

○MXus2.mx1.mailhostbox.com2016-02-09 → 2016-05-09 · 4 obs

● 2016-02-09 11:51:56
● 2016-05-09 05:38:50
○ 2017-01-31 10:06:40
○ 2026-06-07 00:06:18

○MXus2.mx2.mailhostbox.com2016-02-09 → 2016-05-09 · 4 obs

● 2016-02-09 11:51:56
● 2016-05-09 05:38:50
○ 2017-01-31 10:06:40
○ 2026-06-07 00:06:18

○MXus2.mx3.mailhostbox.com2016-02-09 → 2016-05-09 · 4 obs

● 2016-02-09 11:51:56
● 2016-05-09 05:38:50
○ 2017-01-31 10:06:40
○ 2026-06-07 00:06:18

○A128.199.232.2292016-02-09 → 2016-05-09 · 4 obs

● 2016-02-09 11:51:56
● 2016-05-09 05:38:50
○ 2017-01-31 10:06:40
○ 2026-06-07 00:06:18

○A141.8.225.1082017-01-31 → 2017-01-31 · 4 obs

○ 2016-05-09 05:38:50
● 2017-01-31 10:06:40
○ 2018-09-11 18:12:46
○ 2026-06-07 00:06:18

●A54.195.35.2062026-03-17 → 2026-06-07 · 3 obs

○ 2018-09-11 18:12:46
● 2026-03-17 18:14:16
● 2026-06-07 00:06:18

○A72.52.4.1192018-09-11 → 2018-09-11 · 4 obs

○ 2017-01-31 10:06:40
● 2018-09-11 18:12:46
○ 2026-03-17 18:14:16
○ 2026-06-07 00:06:18

○PTRns1381.ztomy.com2017-01-31 → 2017-01-31 · 3 obs

● 2017-01-31 10:06:40
○ 2018-09-11 18:12:46
○ 2026-06-07 00:06:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
execution.in	ns1.daaz.org, ns2.daaz.org	-

✅ Authoritative Response

Server:54.154.209.236

NS records: ns1.daaz.org, ns2.daaz.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for execution.in (unsigned zone)

⏱️ Timing

Total: 659ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.195.35.206`
NS	2	`ns1.daaz.org, ns2.daaz.org`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.execution.in hostmaster.execution.in`

Analysis

IP Addresses

execution.in resolves to just one IP address, 54.195.35.206.

Two other host names, along with eatwell.in, revolvers.in and vqa.in, also share IP numbers with execution.in.

Name Servers

execution.in has three name servers — ns1.execution.in, ns1.daaz.org and ns2.daaz.org.

The name servers of execution.in overlap at least partially with those of other domains — among them gns.my, micro.com.ng, 969.co.in and two more.

These name servers are often deployed in combination with the name servers ns1.gns.my, ns1.micro.com.ng, ns1.969.co.in and six others.

Both ns1.daaz.org and ns2.daaz.org have a single IP address each — ns1.daaz.org resolves to 54.154.209.236 while ns2.daaz.org resolves to 54.72.75.63.