securityservices.in - dns.ninja

`securityservices.in`

DNSSEC	🔒 Signed (DS record present)
A	34.216.117.25^{🇺🇸 Amazon34.208.0.0/12 EC2 PDX prefix}
		PTR	`ec2-34-216-117-25.us-west-2.compute.amazonaws.com`
A	54.149.79.189^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
NS	`launch1.spaceship.net` ⭐
		A	2400:cb00:2049:1::a29f:1a26^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.38^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`launch2.spaceship.net`
		A	2400:cb00:2049:1::a29f:1b20^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.27.32^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`launch1.spaceship.net`support@spaceship.com serial=1770187408

`in`

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

Same first word

DNS History

11 records (4 active, 7 former)

●NSlaunch1.spaceship.net2026-03-09 → 2026-06-26 · 3 obs

○ 2018-08-21 09:46:14
● 2026-03-09 00:03:32
● 2026-06-26 08:14:00

●NSlaunch2.spaceship.net2026-03-09 → 2026-06-26 · 3 obs

○ 2018-08-21 09:46:14
● 2026-03-09 00:03:32
● 2026-06-26 08:14:00

○NSns1.parkingcrew.net2015-06-18 → 2018-08-21 · 4 obs

● 2015-06-18 09:36:50
● 2018-08-21 09:46:14
○ 2026-03-09 00:03:32
○ 2026-06-26 08:14:00

○NSns2.parkingcrew.net2015-06-18 → 2018-08-21 · 4 obs

● 2015-06-18 09:36:50
● 2018-08-21 09:46:14
○ 2026-03-09 00:03:32
○ 2026-06-26 08:14:00

○MXmail.h-email.net2015-06-18 → 2018-08-21 · 4 obs

● 2015-06-18 09:36:50
● 2018-08-21 09:46:14
○ 2026-03-09 00:03:32
○ 2026-06-26 08:14:00

○A185.53.178.72017-01-03 → 2017-01-03 · 4 obs

○ 2016-04-25 04:26:10
● 2017-01-03 03:25:30
○ 2018-08-21 09:46:14
○ 2026-06-26 08:14:00

○A185.53.178.82018-08-21 → 2018-08-21 · 4 obs

○ 2017-01-03 03:25:30
● 2018-08-21 09:46:14
○ 2026-03-09 00:03:32
○ 2026-06-26 08:14:00

○A185.53.179.72015-06-18 → 2016-04-25 · 6 obs

● 2015-06-18 09:36:50
● 2015-11-04 11:35:06
○ 2016-01-25 18:48:14
● 2016-04-25 04:26:10
○ 2017-01-03 03:25:30
○ 2026-06-26 08:14:00

○A185.53.179.92016-01-25 → 2016-01-25 · 4 obs

○ 2015-11-04 11:35:06
● 2016-01-25 18:48:14
○ 2016-04-25 04:26:10
○ 2026-06-26 08:14:00

●A34.216.117.252026-03-09 → 2026-06-26 · 3 obs

○ 2018-08-21 09:46:14
● 2026-03-09 00:03:32
● 2026-06-26 08:14:00

●A54.149.79.1892026-03-09 → 2026-06-26 · 3 obs

○ 2018-08-21 09:46:14
● 2026-03-09 00:03:32
● 2026-06-26 08:14:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns3.registry.in, ns1.registry.in	-
securityservices.in	launch2.spaceship.net, launch1.spaceship.net	-

✅ Authoritative Response

Server:162.159.26.38

NS records: launch2.spaceship.net, launch1.spaceship.net

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 840ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`34.216.117.25, 54.149.79.189`
NS	2	`launch1.spaceship.net, launch2.spaceship.net`
SOA	1	`launch1.spaceship.net support.spaceship.`

Analysis

IP Addresses

securityservices.in has two IP addresses: 34.216.117.25 and 54.149.79.189

personelnet.com, baronmedya.com, sjhomeremodeling.com plus two other host names have IP numbers in common with securityservices.in.

Name Servers

The NS records for securityservices.in delegate to launch1.spaceship.net and launch2.spaceship.net.

The name server configuration of securityservices.in is shared with other domains, for instance tomee.com, hotelcheck.org, vpn24.com and two others.

securityservices.in shares at least some of its name servers with domains including plumbingkelowna.com, lbs.biz and korsco.com

launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. Likewise, launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20 — two IP addresses apiece.