`clientbounty.com`

DNSSEC	⚠️ Not signed
A	147.182.227.165^{🇺🇸 DIGITALOCEAN147.182.224.0/20 DigitalOcean}
		PTR	`1536783.cloudwaysapps.com`
NS	`dns1.registrar-servers.com` ⭐
		A	2610:a1:1024::200^{🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
		A	156.154.132.200^{🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar}
			PTR	`dns1.namecheaphosting.com`
			PTR	`dns1.registrar-servers.com`
NS	`dns2.registrar-servers.com`
		A	2610:a1:1025::200^{🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
		A	156.154.133.200^{🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar}
			PTR	`dns2.namecheaphosting.com`
			PTR	`dns2.registrar-servers.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 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:c01::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`di-in-f27.1e100.net`
		A	74.125.193.27^{🇺🇸 Google74.125.193.0/24}
			PTR	`di-in-f27.1e100.net`
			PTR	`ig-in-f27.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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
TXT	`google-site-verification=jr6ka2t0ZZYbtUWC4SwIFlVY-2Yo13DNHKwQe9Lq79I`
SOA	`dns1.registrar-servers.com`hostmaster@registrar-servers.com serial=1760728671

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

Same first word

clientbounty.com

DNS History

11 records (8 active, 3 former)

○NScns52830.hostwindsdns.com2016-12-18 → 2017-10-14 · 4 obs

● 2016-12-18 22:09:04
● 2017-10-14 00:42:30
○ 2026-03-15 19:12:16
○ 2026-07-31 07:32:10

○NScns52831.hostwindsdns.com2016-12-18 → 2017-10-14 · 4 obs

● 2016-12-18 22:09:04
● 2017-10-14 00:42:30
○ 2026-03-15 19:12:16
○ 2026-07-31 07:32:10

●NSdns1.registrar-servers.com2026-03-15 → 2026-07-31 · 3 obs

○ 2017-10-14 00:42:30
● 2026-03-15 19:12:16
● 2026-07-31 07:32:10

●NSdns2.registrar-servers.com2026-03-15 → 2026-07-31 · 3 obs

○ 2017-10-14 00:42:30
● 2026-03-15 19:12:16
● 2026-07-31 07:32:10

●MXalt1.aspmx.l.google.com2016-12-18 → 2026-07-31 · 2 obs

● 2016-12-18 22:09:04
● 2026-07-31 07:32:10

●MXalt2.aspmx.l.google.com2016-12-18 → 2026-07-31 · 2 obs

● 2016-12-18 22:09:04
● 2026-07-31 07:32:10

●MXalt3.aspmx.l.google.com2016-12-18 → 2026-07-31 · 2 obs

● 2016-12-18 22:09:04
● 2026-07-31 07:32:10

●MXalt4.aspmx.l.google.com2016-12-18 → 2026-07-31 · 2 obs

● 2016-12-18 22:09:04
● 2026-07-31 07:32:10

●MXaspmx.l.google.com2016-12-18 → 2026-07-31 · 2 obs

● 2016-12-18 22:09:04
● 2026-07-31 07:32:10

●A147.182.227.1652026-03-15 → 2026-07-31 · 3 obs

○ 2017-10-14 00:42:30
● 2026-03-15 19:12:16
● 2026-07-31 07:32:10

○A23.254.247.852016-12-18 → 2017-10-14 · 4 obs

● 2016-12-18 22:09:04
● 2017-10-14 00:42:30
○ 2026-03-15 19:12:16
○ 2026-07-31 07:32:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
clientbounty.com	dns1.registrar-servers.com, dns2.registrar-servers.com	4 records

✅ Authoritative Response

Server:156.154.132.200

NS records: dns1.registrar-servers.com, dns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for clientbounty.com (unsigned zone)

⏱️ Timing

Total: 159ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`147.182.227.165`
NS	2	`dns1.registrar-servers.com, dns2.registrar-servers.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`v=spf1 include:_spf.google.com ~all, google-site-verification=jr6ka2t0ZZYbtUW`
SOA	1	`dns1.registrar-servers.com hostmaster.re`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)

Analysis

IP Addresses

clientbounty.com directs to one IP number, which is 147.182.227.165.

htech.com.mx is an example of another host name that shares IP numbers with clientbounty.com.

Name Servers

clientbounty.com has two authoritative name servers — dns1.registrar-servers.com and dns2.registrar-servers.com.

clientbounty.com has the same name server delegation as a number of other domains, such as void.black, bobn.org, isrub.com and two more.

At least some of clientbounty.com's name servers are shared with other domains, for example rufitos.com, amexpo.co, pennsylvaniabikelaw.com and two more.

It is common for these name servers to be used in conjunction with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.

Both dns1.registrar-servers.com and dns2.registrar-servers.com have two IP addresses each. dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200; dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200.