limitcap.com - dns.ninja

`limitcap.com`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-a1.googledomains.com` ⭐
		A	2001:4860:4802:32::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a1.googledomains.com`
		A	216.239.32.106^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-a1.googledomains.com`
NS	`ns-cloud-a2.googledomains.com`
		A	2001:4860:4802:34::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a2.googledomains.com`
		A	216.239.34.106^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-a2.googledomains.com`
NS	`ns-cloud-a3.googledomains.com`
		A	2001:4860:4802:36::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a3.googledomains.com`
		A	216.239.36.106^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-a3.googledomains.com`
NS	`ns-cloud-a4.googledomains.com`
		A	2001:4860:4802:38::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a4.googledomains.com`
		A	216.239.38.106^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-a4.googledomains.com`
SOA	`ns-cloud-a1.googledomains.com`cloud-dns-hostmaster@google.com serial=3

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

WOT: SAFE (50/100)

Previously MX for

limitcap.com

Same first word

limitcap.com

Similar names

tpiclaim.com

icptmail.org

climatip.com

lipmatic.com

plimatic.com

caplimit.com

atilimpc.com

ptcimail.org

tamilpic.com

DNS History

17 records (4 active, 13 former)

○NSdns012.b.register.com2015-12-24 → 2016-03-20 · 5 obs

○ 2015-10-15 02:33:20
● 2015-12-24 03:42:48
● 2016-03-20 21:34:22
○ 2016-09-13 00:24:54
○ 2026-07-05 10:35:04

○NSdns024.c.register.com2015-10-15 → 2015-10-15 · 3 obs

● 2015-10-15 02:33:20
○ 2015-12-24 03:42:48
○ 2026-07-05 10:35:04

○NSdns039.a.register.com2015-12-24 → 2016-03-20 · 5 obs

○ 2015-10-15 02:33:20
● 2015-12-24 03:42:48
● 2016-03-20 21:34:22
○ 2016-09-13 00:24:54
○ 2026-07-05 10:35:04

○NSdns082.d.register.com2015-12-24 → 2016-03-20 · 5 obs

○ 2015-10-15 02:33:20
● 2015-12-24 03:42:48
● 2016-03-20 21:34:22
○ 2016-09-13 00:24:54
○ 2026-07-05 10:35:04

○NSdns139.b.register.com2015-10-15 → 2015-10-15 · 3 obs

● 2015-10-15 02:33:20
○ 2015-12-24 03:42:48
○ 2026-07-05 10:35:04

○NSdns177.d.register.com2015-10-15 → 2015-10-15 · 3 obs

● 2015-10-15 02:33:20
○ 2015-12-24 03:42:48
○ 2026-07-05 10:35:04

○NSdns238.a.register.com2015-10-15 → 2015-10-15 · 3 obs

● 2015-10-15 02:33:20
○ 2015-12-24 03:42:48
○ 2026-07-05 10:35:04

○NSdns239.c.register.com2015-12-24 → 2016-03-20 · 5 obs

○ 2015-10-15 02:33:20
● 2015-12-24 03:42:48
● 2016-03-20 21:34:22
○ 2016-09-13 00:24:54
○ 2026-07-05 10:35:04

●NSns-cloud-a1.googledomains.com2026-04-16 → 2026-07-05 · 3 obs

○ 2016-09-13 00:24:54
● 2026-04-16 19:02:46
● 2026-07-05 10:35:04

●NSns-cloud-a2.googledomains.com2026-04-16 → 2026-07-05 · 3 obs

○ 2016-09-13 00:24:54
● 2026-04-16 19:02:46
● 2026-07-05 10:35:04

●NSns-cloud-a3.googledomains.com2026-04-16 → 2026-07-05 · 3 obs

○ 2016-09-13 00:24:54
● 2026-04-16 19:02:46
● 2026-07-05 10:35:04

●NSns-cloud-a4.googledomains.com2026-04-16 → 2026-07-05 · 3 obs

○ 2016-09-13 00:24:54
● 2026-04-16 19:02:46
● 2026-07-05 10:35:04

○NSsk.s5.ans1.ns148.ztomy.com2016-09-13 → 2016-09-13 · 4 obs

○ 2016-03-20 21:34:22
● 2016-09-13 00:24:54
○ 2026-04-16 19:02:46
○ 2026-07-05 10:35:04

○NSsk.s5.ans2.ns148.ztomy.com2016-09-13 → 2016-09-13 · 4 obs

○ 2016-03-20 21:34:22
● 2016-09-13 00:24:54
○ 2026-04-16 19:02:46
○ 2026-07-05 10:35:04

○MXlimitcap.com2015-10-15 → 2016-03-20 · 4 obs

● 2015-10-15 02:33:20
● 2016-03-20 21:34:22
○ 2016-09-13 00:24:54
○ 2026-07-05 10:35:04

○A208.91.197.462016-09-13 → 2016-09-13 · 4 obs

○ 2016-03-20 21:34:22
● 2016-09-13 00:24:54
○ 2026-04-16 19:02:46
○ 2026-07-05 10:35:04

○A43.225.104.1732015-10-15 → 2016-03-20 · 4 obs

● 2015-10-15 02:33:20
● 2016-03-20 21:34:22
○ 2016-09-13 00:24:54
○ 2026-07-05 10:35:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, c.gtld-servers.net, i.gtld-servers.net, a.gtld-servers.net...	-
limitcap.com	ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.38.106

NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for limitcap.com (unsigned zone)

⏱️ Timing

Total: 225ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-a1.googledomains.com, ns-cloud-a3.googledomains.com...`
SOA	1	`ns-cloud-a1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)

Analysis

Name Servers

Four name servers handle the delegation for limitcap.com: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.

At least some of limitcap.com's name servers are shared with other domains, for example sandrayao.com, themagicalmysterytour.net, mdij.com and two more.

Four hostnames, each resolving to a pair of IP addresses: ns-cloud-a1.googledomains.com directs to 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com directs to 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com directs to 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com directs to 216.239.38.106 and 2001:4860:4802:38::6a.