clientbounty.com - dns.ninja
clientbounty.com
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.netnstld@verisign-grs.com serial=1783781302 | ||||||
Same first word
clientbounty.com |
DNS History
11 records (8 active, 3 former)
○NScns52830.hostwindsdns.com2016-12-18 → 2017-10-14 · 4 obs
● 2017-10-14 00:42:30
○ 2026-03-15 19:12:16
○ 2026-07-11 14:54:58
○NScns52831.hostwindsdns.com2016-12-18 → 2017-10-14 · 4 obs
● 2017-10-14 00:42:30
○ 2026-03-15 19:12:16
○ 2026-07-11 14:54:58
●NSdns1.registrar-servers.com2026-03-15 → 2026-07-11 · 3 obs
● 2026-03-15 19:12:16
● 2026-07-11 14:54:58
●NSdns2.registrar-servers.com2026-03-15 → 2026-07-11 · 3 obs
● 2026-03-15 19:12:16
● 2026-07-11 14:54:58
●MXalt1.aspmx.l.google.com2016-12-18 → 2026-07-11 · 2 obs
● 2026-07-11 14:54:58
●MXalt2.aspmx.l.google.com2016-12-18 → 2026-07-11 · 2 obs
● 2026-07-11 14:54:58
●MXalt3.aspmx.l.google.com2016-12-18 → 2026-07-11 · 2 obs
● 2026-07-11 14:54:58
●MXalt4.aspmx.l.google.com2016-12-18 → 2026-07-11 · 2 obs
● 2026-07-11 14:54:58
●MXaspmx.l.google.com2016-12-18 → 2026-07-11 · 2 obs
● 2026-07-11 14:54:58
●A147.182.227.1652026-03-15 → 2026-07-11 · 3 obs
● 2026-03-15 19:12:16
● 2026-07-11 14:54:58
○A23.254.247.852016-12-18 → 2017-10-14 · 4 obs
● 2017-10-14 00:42:30
○ 2026-03-15 19:12:16
○ 2026-07-11 14:54:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| clientbounty.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.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: 183ms | 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 resolves to one IP address: 147.182.227.165.
Among the host names that share IP numbers with clientbounty.com is htech.com.mx, as one example.
Name Servers
The NS records for clientbounty.com delegate to dns1.registrar-servers.com and dns2.registrar-servers.com.
clientbounty.com uses the same name servers as several other domains — among them void.black, bobn.org, isrub.com and two more.
clientbounty.com has at least partial name server overlap with other domains, such as rufitos.com, amexpo.co, pennsylvaniabikelaw.com and two others.
These name servers tend to appear together with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200. Likewise, dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200 — two IP addresses apiece.
Mail Servers
Mail for clientbounty.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
clientbounty.com has at least partial mail server overlap with other domains such as ns500731.ns500671.ns500731.ns500671.ns500742.ns500731.ns500671.ns500688.ns500705.ns500671.ns500649.ns500649.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500742.ns500671.ns500754.ns500754.ns500671.ns500671.ns500688.ns500649.ns500688.ns500678.ns500666.ns500142.lusty(0x736c7574)z.com, ns500693.ns500693.ns500734.ns500699.ns500693.ns500734.ns500734.ns500699.ns500693.ns500588.ns500612.ns500588.ns500110.dtrkdll.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
The A records for aspmx.l.google.com return 192.178.155.27 and 2607:f8b0:4004:c21::1b.
The A records for alt1.aspmx.l.google.com return 108.177.123.26 and 2800:3f0:4003:c0f::1b.
The A records for alt2.aspmx.l.google.com return 172.253.116.26 and 2a00:1450:400b:c02::1a.
The A records for alt3.aspmx.l.google.com return 192.178.223.26 and 2a00:1450:4009:c0f::1a.
The A records for alt4.aspmx.l.google.com return 172.253.157.27 and 2a00:1450:400c:c23::1b.