readwrite.in - dns.ninja

`readwrite.in`

DNSSEC	⚠️ Not signed
A	2a02:4780:11:1768:0:28ba:a694:2^{🇮🇳 IIHOS0012a02:4780:11::/48 HOSTINGER IN}
A	82.112.239.186^{🇬🇧 IIHOS00182.112.224.0/20 HOSTINGER IN}
NS	`ns1.dns-parking.com` ⭐
		A	2400:cb00:2049:1::a29f:18c9^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.201^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dns-parking.com`
NS	`ns2.dns-parking.com`
		A	2400:cb00:2049:1::a29f:192a^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.25.42^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dns-parking.com`
MX	`mx1.hostinger.in` ⭐
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`mx2.hostinger.in`⁽¹⁰⁾
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
TXT	`v=spf1 include:_spf.mail.hostinger.com ~all`
SOA	`ns1.dns-parking.com`dns@hostinger.com 2026-06-25 #1

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

Subdomains

www.readwrite.in

Same first word

readwrite.eu

readwrite.org

readwrite.nl

readwrite.digital

readwrite.ru

readwrite.co.uk

readwrite.wiki

readwrite.it

readwrite.net

readwrite.com

readwrite.de

readwrite.in

readwrite.me.uk

Similar names

DNS History

16 records (6 active, 10 former)

○NScns1.my-hosting-panel.com2020-01-10 → 2020-01-10 · 4 obs

○ 2017-03-13 15:20:28
● 2020-01-10 10:22:10
○ 2026-02-20 13:46:26
○ 2026-06-25 18:02:18

○NScns2.my-hosting-panel.com2020-01-10 → 2020-01-10 · 4 obs

○ 2017-03-13 15:20:28
● 2020-01-10 10:22:10
○ 2026-02-20 13:46:26
○ 2026-06-25 18:02:18

●NSns1.dns-parking.com2026-02-20 → 2026-06-25 · 3 obs

○ 2020-01-10 10:22:10
● 2026-02-20 13:46:26
● 2026-06-25 18:02:18

○NSns1.netnames.net2015-08-17 → 2017-03-13 · 4 obs

● 2015-08-17 20:11:02
● 2017-03-13 15:20:28
○ 2020-01-10 10:22:10
○ 2026-06-25 18:02:18

●NSns2.dns-parking.com2026-02-20 → 2026-06-25 · 3 obs

○ 2020-01-10 10:22:10
● 2026-02-20 13:46:26
● 2026-06-25 18:02:18

○NSns2.netnames.net2015-08-17 → 2017-03-13 · 4 obs

● 2015-08-17 20:11:02
● 2017-03-13 15:20:28
○ 2020-01-10 10:22:10
○ 2026-06-25 18:02:18

○NSns5.netnames.net2015-08-17 → 2017-03-13 · 4 obs

● 2015-08-17 20:11:02
● 2017-03-13 15:20:28
○ 2020-01-10 10:22:10
○ 2026-06-25 18:02:18

○NSns6.netnames.net2015-08-17 → 2017-03-13 · 4 obs

● 2015-08-17 20:11:02
● 2017-03-13 15:20:28
○ 2020-01-10 10:22:10
○ 2026-06-25 18:02:18

●MXmx1.hostinger.in2026-02-20 → 2026-06-25 · 3 obs

○ 2020-01-10 10:22:10
● 2026-02-20 13:46:26
● 2026-06-25 18:02:18

●MXmx2.hostinger.in2026-02-20 → 2026-06-25 · 3 obs

○ 2020-01-10 10:22:10
● 2026-02-20 13:46:26
● 2026-06-25 18:02:18

○MXrelay1.netnames.net2015-08-17 → 2017-03-13 · 4 obs

● 2015-08-17 20:11:02
● 2017-03-13 15:20:28
○ 2020-01-10 10:22:10
○ 2026-06-25 18:02:18

○MXrelay2.netnames.net2015-08-17 → 2017-03-13 · 4 obs

● 2015-08-17 20:11:02
● 2017-03-13 15:20:28
○ 2020-01-10 10:22:10
○ 2026-06-25 18:02:18

○A185.26.230.1292015-08-17 → 2017-03-13 · 4 obs

● 2015-08-17 20:11:02
● 2017-03-13 15:20:28
○ 2020-01-10 10:22:10
○ 2026-06-25 18:02:18

○A204.93.172.292020-01-10 → 2020-01-10 · 4 obs

○ 2017-03-13 15:20:28
● 2020-01-10 10:22:10
○ 2026-02-20 13:46:26
○ 2026-06-25 18:02:18

●A2a02:4780:11:1768:0:28ba:a694:22026-02-20 → 2026-06-25 · 3 obs

○ 2020-01-10 10:22:10
● 2026-02-20 13:46:26
● 2026-06-25 18:02:18

●A82.112.239.1862026-02-20 → 2026-06-25 · 3 obs

○ 2020-01-10 10:22:10
● 2026-02-20 13:46:26
● 2026-06-25 18:02:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns3.registry.in, ns1.registry.in	-
readwrite.in	ns1.dns-parking.com, ns2.dns-parking.com	-

✅ Authoritative Response

Server:162.159.25.42

NS records: ns1.dns-parking.com, ns2.dns-parking.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for readwrite.in (unsigned zone)

⏱️ Timing

Total: 2270ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`82.112.239.186`
AAAA	1	`2a02:4780:11:1768:0:28ba:a694:2`
NS	2	`ns1.dns-parking.com, ns2.dns-parking.com`
MX	2	`mx2.hostinger.in (pri: 10), mx1.hostinger.in (pri: 5)`
TXT	1	`v=spf1 include:_spf.mail.hostinger.com ~`
SOA	1	`ns1.dns-parking.com dns.hostinger.com`

Analysis

Hierarchy

www.readwrite.in is delegated beneath readwrite.in.

IP Addresses

readwrite.in has two IP addresses: 82.112.239.186 and 2a02:4780:11:1768:0:28ba:a694:2

Host names like morescouture.com are further examples that share IP numbers with readwrite.in.

Name Servers

Two name servers handle the delegation for readwrite.in: ns1.dns-parking.com and ns2.dns-parking.com.

readwrite.in uses the same name servers as several other domains — among them ecommerce360services.com, moumoving.com, bola-mania.com and two more.

readwrite.in is at least partially co-delegated on name servers with other domains, such as institutoquintana.com.ar.

ns1.dns-parking.com and ns2.dns-parking.com both carry two IP addresses. The A records for ns1.dns-parking.com are 162.159.24.201 and 2400:cb00:2049:1::a29f:18c9; the A records for ns2.dns-parking.com are 162.159.25.42 and 2400:cb00:2049:1::a29f:192a.

Mail Servers

Mail for readwrite.in is handled by two mail servers — mx1.hostinger.in and mx2.hostinger.in.

readwrite.in uses an identical mail server configuration to several other domains — among them press-journal.com, apartmentrentalnearme.ca, onlineappsdba.com and two more.

readwrite.in has at least partial mail server overlap with other domains such as aavantbackdrops.com, bmjnsg.com, littlewish.in and two more.

mx1.hostinger.in and mx2.hostinger.in each point to two IP numbers — 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f — making both hosts identical in their DNS resolution.

mx1.hostinger.in along with mx2.hostinger.in each resolve to 2606:4700:90:0:c1f8:f874:2386:b61f IP addresses.

mx1.hostinger.in along with mx2.hostinger.in each resolve to 172.65.182.103 IP addresses.