`jpmanage.net`

DNSSEC	🔒 Signed (DS record present)
A	132.148.183.172^{🇺🇸 AS398101132.148.176.0/21}
		PTR	`172.183.148.132.host.secureserver.net`
NS	`ns-cloud-b1.googledomains.com` ⭐
		A	2001:4860:4802:32::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b1.googledomains.com`
		A	216.239.32.107^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-b1.googledomains.com`
NS	`ns-cloud-b2.googledomains.com`
		A	2001:4860:4802:34::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b2.googledomains.com`
		A	216.239.34.107^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-b2.googledomains.com`
NS	`ns-cloud-b3.googledomains.com`
		A	2001:4860:4802:36::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b3.googledomains.com`
		A	216.239.36.107^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-b3.googledomains.com`
NS	`ns-cloud-b4.googledomains.com`
		A	2001:4860:4802:38::6b^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-b4.googledomains.com`
		A	216.239.38.107^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-b4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c27::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f27.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:3003::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f27.1e100.net`
		A	172.253.145.26^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.27^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns-cloud-b1.googledomains.com`cloud-dns-hostmaster@google.com serial=4

`net`

	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=1778648397

rank #354785 globally
rank #9606 in the tld

Same first word

jpmanage.net

Similar names

jampagne.com

megjapan.com

DNS History

10 records (10 active, 0 former)

●NSns-cloud-b1.googledomains.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●NSns-cloud-b2.googledomains.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●NSns-cloud-b3.googledomains.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●NSns-cloud-b4.googledomains.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●MXalt1.aspmx.l.google.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●MXalt2.aspmx.l.google.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●MXalt3.aspmx.l.google.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●MXalt4.aspmx.l.google.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●MXaspmx.l.google.com2026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

●A132.148.183.1722026-03-23 → 2026-05-13 · 2 obs

● 2026-03-23 09:04:28
● 2026-05-13 05:10:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
jpmanage.net	ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com	-

✅ Authoritative Response

Server:216.239.38.107

NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 668ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`132.148.183.172`
NS	4	`ns-cloud-b2.googledomains.com, ns-cloud-b4.googledomains.com...`
MX	5	`alt2.aspmx.l.google.com (pri: 5), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns-cloud-b1.googledomains.com cloud-dns-`

Analysis

IP Addresses

jpmanage.net points to a single IP: 132.148.183.172.

Other host names, for instance happlessrecords.com, dastaavej.com, sindhicollege.in, ldc.com.lb and 172.183.148.132.host.secureserver.net share IP numbers with jpmanage.net.

Name Servers

jpmanage.net's delegation is handled by four name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.

jpmanage.net partially shares name servers with other domains; examples include getswurl.com, towlescourt.com, mlbandassoc.com, gatesofsplendor.net and choicepoint.info.

Host names with two IPs:

ns-cloud-b1.googledomains.com points to 2001:4860:4802:32::6b and 216.239.32.107

ns-cloud-b2.googledomains.com points to 2001:4860:4802:34::6b and 216.239.34.107

ns-cloud-b3.googledomains.com points to 2001:4860:4802:36::6b and 216.239.36.107

ns-cloud-b4.googledomains.com points to 2001:4860:4802:38::6b and 216.239.38.107

Mail Servers

Five mail servers handle jpmanage.net: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

jpmanage.net shares some mail servers with other domains, at least partially, such as dnki.net, devincarlson.ca, iima.co.jp, inmobiliariarg.com and lqdent.com.sg.