jrdgroup.com - dns.ninja

`jrdgroup.com`

DNSSEC	⚠️ Not signed
A	52.60.87.163^{🇨🇦 Amazon52.60.64.0/18}
		PTR	`ec2-52-60-87-163.ca-central-1.compute.amazonaws.com`
NS	`ns1.101domain.com` ⭐
		A	2400:cb00:2049:1::a29f:18ca^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
			PTR	`ns1.101domain.com`
		A	162.159.24.202^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.101domain.com`
NS	`ns2.101domain.com`
		A	2400:cb00:2049:1::a29f:199c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
			PTR	`ns2.101domain.com`
		A	162.159.25.156^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.101domain.com`
NS	`ns5.101domain.com` ⚠️ Not in parent delegation
		A	2400:cb00:2049:1::a29f:18ca^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
			PTR	`ns1.101domain.com`
		A	2400:cb00:2049:1::a29f:199c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
			PTR	`ns2.101domain.com`
		A	162.159.24.202^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.101domain.com`
		A	162.159.25.156^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.101domain.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	172.253.115.27^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-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	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
SOA	`ns1.101domain.com`ADMIN@jrdgroup.com 2021-05-10 #5

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

Same first word

jrdgroup.com

Similar names

drjgroup.com

grupojdr.com

jdrgroup.co.uk

rjdgroup.in

jdrgroup.com

drjgroup.org

rdjgroup.com

DNS History

23 records (9 active, 14 former)

○NSns-1075.awsdns-06.org2026-04-03 → 2026-04-03 · 4 obs

○ 2020-01-22 17:18:28
● 2026-04-03 09:48:18
○ 2026-07-23 15:49:08
○ 2026-07-23 15:49:10

○NSns-1687.awsdns-18.co.uk2026-04-03 → 2026-04-03 · 4 obs

○ 2020-01-22 17:18:28
● 2026-04-03 09:48:18
○ 2026-07-23 15:49:08
○ 2026-07-23 15:49:10

○NSns-383.awsdns-47.com2026-04-03 → 2026-04-03 · 4 obs

○ 2020-01-22 17:18:28
● 2026-04-03 09:48:18
○ 2026-07-23 15:49:08
○ 2026-07-23 15:49:10

○NSns-784.awsdns-34.net2026-04-03 → 2026-04-03 · 4 obs

○ 2020-01-22 17:18:28
● 2026-04-03 09:48:18
○ 2026-07-23 15:49:08
○ 2026-07-23 15:49:10

○NSns0.dnsmadeeasy.com2015-05-07 → 2020-01-22 · 4 obs

● 2015-05-07 22:59:28
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

●NSns1.101domain.com2026-07-23 → 2026-07-23 · 3 obs

○ 2026-04-03 09:48:18
● 2026-07-23 15:49:08
● 2026-07-23 15:49:10

○NSns1.dnsmadeeasy.com2015-05-07 → 2020-01-22 · 4 obs

● 2015-05-07 22:59:28
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

●NSns2.101domain.com2026-07-23 → 2026-07-23 · 3 obs

○ 2026-04-03 09:48:18
● 2026-07-23 15:49:08
● 2026-07-23 15:49:10

○NSns2.dnsmadeeasy.com2015-05-07 → 2020-01-22 · 4 obs

● 2015-05-07 22:59:28
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

○NSns3.dnsmadeeasy.com2015-05-07 → 2020-01-22 · 4 obs

● 2015-05-07 22:59:28
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

○NSns4.dnsmadeeasy.com2015-05-07 → 2020-01-22 · 4 obs

● 2015-05-07 22:59:28
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

●NSns5.101domain.com2026-07-23 → 2026-07-23 · 3 obs

○ 2026-04-03 09:48:18
● 2026-07-23 15:49:08
● 2026-07-23 15:49:10

●MXalt1.aspmx.l.google.com2015-05-07 → 2026-07-23 · 2 obs

● 2015-05-07 22:59:28
● 2026-07-23 15:49:10

●MXalt2.aspmx.l.google.com2015-05-07 → 2026-07-23 · 2 obs

● 2015-05-07 22:59:28
● 2026-07-23 15:49:10

○MXalt3.aspmx.l.google.com2015-05-07 → 2020-01-22 · 4 obs

● 2015-05-07 22:59:28
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

○MXalt4.aspmx.l.google.com2015-05-07 → 2020-01-22 · 4 obs

● 2015-05-07 22:59:28
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

○MXaspmx.google.com2015-05-07 → 2020-01-22 · 4 obs

● 2015-05-07 22:59:28
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

●MXaspmx.l.google.com2026-04-03 → 2026-07-23 · 3 obs

○ 2020-01-22 17:18:28
● 2026-04-03 09:48:18
● 2026-07-23 15:49:10

●MXaspmx2.googlemail.com2026-04-03 → 2026-07-23 · 3 obs

○ 2020-01-22 17:18:28
● 2026-04-03 09:48:18
● 2026-07-23 15:49:10

●MXaspmx3.googlemail.com2026-04-03 → 2026-07-23 · 3 obs

○ 2020-01-22 17:18:28
● 2026-04-03 09:48:18
● 2026-07-23 15:49:10

○A173.199.130.2322015-05-07 → 2016-01-04 · 4 obs

● 2015-05-07 22:59:28
● 2016-01-04 11:31:22
○ 2016-01-05 12:05:52
○ 2026-07-23 15:49:10

○A178.79.137.1902016-01-05 → 2020-01-22 · 5 obs

○ 2016-01-04 11:31:22
● 2016-01-05 12:05:52
● 2020-01-22 17:18:28
○ 2026-04-03 09:48:18
○ 2026-07-23 15:49:10

●A52.60.87.1632026-07-23 → 2026-07-23 · 3 obs

○ 2026-04-03 09:48:18
● 2026-07-23 15:49:08
● 2026-07-23 15:49:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net...	-
jrdgroup.com	ns1.101domain.com, ns2.101domain.com	4 records

✅ Authoritative Response

Server:162.159.25.156

NS records: ns1.101domain.com, ns2.101domain.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for jrdgroup.com (unsigned zone)

⏱️ Timing

Total: 402ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.60.87.163`
NS	3	`ns1.101domain.com, ns2.101domain.com...`
MX	5	`alt2.aspmx.l.google.com (pri: 5), alt1.aspmx.l.google.com (pri: 5)...`
SOA	1	`ns1.101domain.com ADMIN.jrdgroup.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.101domain.com, ns1.101domain.com, ns2.101domain.com...)

Analysis

IP Addresses

jrdgroup.com resolves to just one IP address, 52.60.87.163.

Two other host names, along with legitnews.ng, steelcase.pe and woods.shopping, also share IP numbers with jrdgroup.com.

Name Servers

jrdgroup.com carries NS records delegating to ns1.101domain.com, ns2.101domain.com and ns5.101domain.com.

jrdgroup.com has at least partial name server overlap with other domains, such as costatropicalhotels.net, intelligentinsoles.com, toplessanchors.com and two others.

It is common to see these name servers used together with name servers ns2.rwgusa.net and ns.rwgusa.net.

Host names that resolve to four IP numbers:

ns5.101domain.com has four IP addresses: 162.159.24.202, 162.159.25.156, 2400:cb00:2049:1::a29f:18ca and 2400:cb00:2049:1::a29f:199c.

Host names that have two IP addresses:

ns1.101domain.com resolves to two addresses: 162.159.24.202 and 2400:cb00:2049:1::a29f:18ca.

ns2.101domain.com resolves to two addresses: 162.159.25.156 and 2400:cb00:2049:1::a29f:199c.

ns5.101domain.com along with ns1.101domain.com each resolve to 2400:cb00:2049:1::a29f:18ca IP addresses.

ns5.101domain.com along with ns2.101domain.com each resolve to 2400:cb00:2049:1::a29f:199c IP addresses.

ns5.101domain.com along with ns1.101domain.com each resolve to 162.159.24.202 IP addresses.

ns5.101domain.com along with ns2.101domain.com each resolve to 162.159.25.156 IP addresses.

Mail Servers

jrdgroup.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between jrdgroup.com and other domains, including applicationcraft.com, ns500754.ns500742.ns500754.ns500754.ns500671.ns500731.ns500705.ns500688.ns500678.ns500678.ns500649.ns500649.ns500153.tenderladiesbz.com, ns500698.ns500758.ns500759.ns500736.ns500735.ns500736.ns500735.ns500576.ns500698.ns500708.trackreceptor.com and two others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com resolves to two addresses: 172.253.115.27 and 2607:f8b0:4004:c23::1b.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.

aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 172.253.116.26 IP addresses.