`systemcare.in.net`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:343c^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3030::ac43:c3f6^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.52.60^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.195.246^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`denver.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2cc4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3c4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`denver.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23c4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`denver.ns.cloudflare.com`
		A	108.162.195.196^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	162.159.44.196^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	172.64.35.196^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
NS	`susan.ns.cloudflare.com`
		A	2606:4700:50::a29f:26c7^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`susan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2c7^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`susan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22c7^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`susan.ns.cloudflare.com`
		A	108.162.194.199^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`susan.ns.cloudflare.com`
		A	162.159.38.199^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`susan.ns.cloudflare.com`
		A	172.64.34.199^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`susan.ns.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.52.60, 172.67.195.246
		IPv6 hints	2606:4700:3030::6815:343c, 2606:4700:3030::ac43:c3f6
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=0, name=cloudflare-ech.com
SOA	`denver.ns.cloudflare.com`dns@cloudflare.com serial=2402527103

`in.net`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1777222120

rank #392 globally
rank #10 in the tld
This domain "in.net" is a top-level domain name that can be used by individuals or organizations globally without any restrictions. It caters to a broad audience and is not country-specific or industry-specific. The ".net" extension suggests that it could be ideal for technology or internet-based businesses, but it's open for any usage.📈 Tranco rank: #1,781

Previously MX for

systemcare.in.net

Same first word

systemcare.sg

systemcare.in

systemcare.nl

systemcare.org

systemcare.co.uk

systemcare.com.my

systemcare.co.in

systemcare.ca

systemcare.info

systemcare.jp

systemcare.com.au

systemcare.de

systemcare.eu

systemcare.com

systemcare.dk

systemcare.in.net

Similar names

DNS History

10 records (6 active, 4 former)

●NSdenver.ns.cloudflare.com2026-03-24 → 2026-04-26 · 3 obs

○ 2020-01-18 18:38:00
● 2026-03-24 08:52:10
● 2026-04-26 17:12:24

○NSns3.amuhost.com2020-01-18 → 2020-01-18 · 3 obs

● 2020-01-18 18:38:00
○ 2026-03-24 08:52:10
○ 2026-04-26 17:12:24

○NSns4.amuhost.com2020-01-18 → 2020-01-18 · 3 obs

● 2020-01-18 18:38:00
○ 2026-03-24 08:52:10
○ 2026-04-26 17:12:24

●NSsusan.ns.cloudflare.com2026-03-24 → 2026-04-26 · 3 obs

○ 2020-01-18 18:38:00
● 2026-03-24 08:52:10
● 2026-04-26 17:12:24

○MXsystemcare.in.net2020-01-18 → 2020-01-18 · 3 obs

● 2020-01-18 18:38:00
○ 2026-03-24 08:52:10
○ 2026-04-26 17:12:24

●A104.21.52.602026-03-24 → 2026-04-26 · 3 obs

○ 2020-01-18 18:38:00
● 2026-03-24 08:52:10
● 2026-04-26 17:12:24

●A172.67.195.2462026-03-24 → 2026-04-26 · 3 obs

○ 2020-01-18 18:38:00
● 2026-03-24 08:52:10
● 2026-04-26 17:12:24

●A2606:4700:3030::6815:343c2026-03-24 → 2026-04-26 · 3 obs

○ 2020-01-18 18:38:00
● 2026-03-24 08:52:10
● 2026-04-26 17:12:24

●A2606:4700:3030::ac43:c3f62026-03-24 → 2026-04-26 · 3 obs

○ 2020-01-18 18:38:00
● 2026-03-24 08:52:10
● 2026-04-26 17:12:24

○A88.99.165.1762020-01-18 → 2020-01-18 · 3 obs

● 2020-01-18 18:38:00
○ 2026-03-24 08:52:10
○ 2026-04-26 17:12:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
in.net	ns10.trs-dns.info, ns10.trs-dns.org, ns01.trs-dns.com, ns01.trs-dns.net	2 records
systemcare.in.net	denver.ns.cloudflare.com, susan.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.38.199

NS records: denver.ns.cloudflare.com, susan.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for systemcare.in.net (unsigned zone)

⏱️ Timing

Total: 590ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.195.246, 104.21.52.60`
AAAA	2	`2606:4700:3030::ac43:c3f6, 2606:4700:3030::6815:343c`
NS	2	`denver.ns.cloudflare.com, susan.ns.cloudflare.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`denver.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns01.trs-dns.net, ns01.trs-dns.net)

Analysis

IP Addresses

systemcare.in.net maps to four IP numbers: 2606:4700:3030::6815:343c, 2606:4700:3030::ac43:c3f6, 104.21.52.60 and 172.67.195.246.

Other host names, for instance www.webkech.com, uninfector.com, adminlaw.org.uk, rjhnursingalum.com and www.entegreturk.com share IP numbers with systemcare.in.net.

Name Servers

Two name servers denver.ns.cloudflare.com and susan.ns.cloudflare.com handle delegation for systemcare.in.net.

systemcare.in.net uses the same name server setup as other domains, for example financehub.za.com, homefarm.uk.net, grunter.ru.com, web2edu.ru.com and sohu.us.com.

systemcare.in.net partially shares name servers with other domains; examples include fefe66.com, theskyclubhouse.com, jobbank.com.tw, cyber-nest.sbs and gdppm.com.

These name servers are often used with the name servers noel.ns.cloudflare.com and damon.ns.cloudflare.com.

Host names with six IP numbers: denver.ns.cloudflare.com points to: 2606:4700:58::a29f:2cc4, 2803:f800:50::6ca2:c3c4, 2a06:98c1:50::ac40:23c4, 108.162.195.196, 162.159.44.196 and 172.64.35.196; susan.ns.cloudflare.com points to: 2606:4700:50::a29f:26c7, 2803:f800:50::6ca2:c2c7, 2a06:98c1:50::ac40:22c7, 108.162.194.199, 162.159.38.199 and 172.64.34.199.

systemcare.in.net - robtex.com