hedgeradar.com - robtex.com

hedgeradar.com

DNSSEC⚠️ Not signed
A13.248.169.48πŸ‡ΊπŸ‡Έ Amazon13.248.160.0/20
PTRa904c694c05102f30.awsglobalaccelerator.com
A76.223.54.146πŸ‡ΊπŸ‡Έ Amazon76.223.48.0/20
NSns3.afternic.com ⭐
A97.74.98.65πŸ‡ΊπŸ‡Έ GODADDY-DNS97.74.98.0/23
PTRns3.afternic.com
NSns4.afternic.com
A173.201.66.65πŸ‡ΊπŸ‡Έ GODADDY-DNS173.201.66.0/23
PTRns4.namefind.com
TXTv=spf1 -all
SOAns3.afternic.comdns@jomax.net 2025-10-01 #0

com

Same first word

DNS History

21 records (4 active, 17 former)

20192020202120222023202420252026NSns3.afternic.comns4.afternic.comdns1.name-services.comdns1.registrar-servers.comdns2.name-services.comdns2.registrar-servers.comdns3.name-services.comdns4.name-services.comdns5.name-services.comns1.atom.comns2.atom.comMXeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA13.248.169.4876.223.54.14615.197.212.58162.255.119.15452.20.84.62
β—‹NSdns1.name-services.com2026-05-02 β†’ 2026-05-02 Β· 4 obs
β—‹ 2026-03-28 08:50:12
● 2026-05-02 12:09:30
β—‹ 2026-06-17 11:07:10
β—‹ 2026-07-15 07:46:24
β—‹NSdns1.registrar-servers.com2018-06-21 β†’ 2018-06-21 Β· 3 obs
● 2018-06-21 15:44:44
β—‹ 2026-03-03 16:59:56
β—‹ 2026-07-15 07:46:24
β—‹NSdns2.name-services.com2026-05-02 β†’ 2026-05-02 Β· 4 obs
β—‹ 2026-03-28 08:50:12
● 2026-05-02 12:09:30
β—‹ 2026-06-17 11:07:10
β—‹ 2026-07-15 07:46:24
β—‹NSdns2.registrar-servers.com2018-06-21 β†’ 2018-06-21 Β· 3 obs
● 2018-06-21 15:44:44
β—‹ 2026-03-03 16:59:56
β—‹ 2026-07-15 07:46:24
β—‹NSdns3.name-services.com2026-05-02 β†’ 2026-05-02 Β· 4 obs
β—‹ 2026-03-28 08:50:12
● 2026-05-02 12:09:30
β—‹ 2026-06-17 11:07:10
β—‹ 2026-07-15 07:46:24
β—‹NSdns4.name-services.com2026-05-02 β†’ 2026-05-02 Β· 4 obs
β—‹ 2026-03-28 08:50:12
● 2026-05-02 12:09:30
β—‹ 2026-06-17 11:07:10
β—‹ 2026-07-15 07:46:24
β—‹NSdns5.name-services.com2026-05-02 β†’ 2026-05-02 Β· 4 obs
β—‹ 2026-03-28 08:50:12
● 2026-05-02 12:09:30
β—‹ 2026-06-17 11:07:10
β—‹ 2026-07-15 07:46:24
β—‹NSns1.atom.com2026-03-03 β†’ 2026-03-28 Β· 5 obs
β—‹ 2018-06-21 15:44:44
● 2026-03-03 16:59:56
● 2026-03-28 08:50:12
β—‹ 2026-05-02 12:09:30
β—‹ 2026-07-15 07:46:24
β—‹NSns2.atom.com2026-03-03 β†’ 2026-03-28 Β· 5 obs
β—‹ 2018-06-21 15:44:44
● 2026-03-03 16:59:56
● 2026-03-28 08:50:12
β—‹ 2026-05-02 12:09:30
β—‹ 2026-07-15 07:46:24
●NSns3.afternic.com2026-06-17 β†’ 2026-07-15 Β· 3 obs
β—‹ 2026-05-02 12:09:30
● 2026-06-17 11:07:10
● 2026-07-15 07:46:24
●NSns4.afternic.com2026-06-17 β†’ 2026-07-15 Β· 3 obs
β—‹ 2026-05-02 12:09:30
● 2026-06-17 11:07:10
● 2026-07-15 07:46:24
β—‹MXeforward1.registrar-servers.com2018-06-21 β†’ 2018-06-21 Β· 3 obs
● 2018-06-21 15:44:44
β—‹ 2026-03-03 16:59:56
β—‹ 2026-07-15 07:46:24
β—‹MXeforward2.registrar-servers.com2018-06-21 β†’ 2018-06-21 Β· 3 obs
● 2018-06-21 15:44:44
β—‹ 2026-03-03 16:59:56
β—‹ 2026-07-15 07:46:24
β—‹MXeforward3.registrar-servers.com2018-06-21 β†’ 2018-06-21 Β· 3 obs
● 2018-06-21 15:44:44
β—‹ 2026-03-03 16:59:56
β—‹ 2026-07-15 07:46:24
β—‹MXeforward4.registrar-servers.com2018-06-21 β†’ 2018-06-21 Β· 3 obs
● 2018-06-21 15:44:44
β—‹ 2026-03-03 16:59:56
β—‹ 2026-07-15 07:46:24
β—‹MXeforward5.registrar-servers.com2018-06-21 β†’ 2018-06-21 Β· 3 obs
● 2018-06-21 15:44:44
β—‹ 2026-03-03 16:59:56
β—‹ 2026-07-15 07:46:24
●A13.248.169.482026-06-17 β†’ 2026-07-15 Β· 3 obs
β—‹ 2026-05-02 12:09:30
● 2026-06-17 11:07:10
● 2026-07-15 07:46:24
β—‹A15.197.212.582026-05-02 β†’ 2026-05-02 Β· 4 obs
β—‹ 2026-03-28 08:50:12
● 2026-05-02 12:09:30
β—‹ 2026-06-17 11:07:10
β—‹ 2026-07-15 07:46:24
β—‹A162.255.119.1542018-06-21 β†’ 2018-06-21 Β· 3 obs
● 2018-06-21 15:44:44
β—‹ 2026-03-03 16:59:56
β—‹ 2026-07-15 07:46:24
β—‹A52.20.84.622026-03-03 β†’ 2026-03-28 Β· 5 obs
β—‹ 2018-06-21 15:44:44
● 2026-03-03 16:59:56
● 2026-03-28 08:50:12
β—‹ 2026-05-02 12:09:30
β—‹ 2026-07-15 07:46:24
●A76.223.54.1462026-06-17 β†’ 2026-07-15 Β· 3 obs
β—‹ 2026-05-02 12:09:30
● 2026-06-17 11:07:10
● 2026-07-15 07:46:24

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
comk.gtld-servers.net, b.gtld-servers.net, l.gtld-servers.net, h.gtld-servers.net...-
hedgeradar.comns3.afternic.com, ns4.afternic.com2 records

βœ… Authoritative Response

Server:173.201.66.65

NS records: ns3.afternic.com, ns4.afternic.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hedgeradar.com (unsigned zone)

⏱️ Timing

Total: 143ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A213.248.169.48, 76.223.54.146
NS2ns3.afternic.com, ns4.afternic.com
MX1. (pri: 0)
TXT1v=spf1 -all
SOA1ns3.afternic.com dns.jomax.net

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns3.afternic.com, ns4.afternic.com)

Analysis

IP Addresses

hedgeradar.com directs to two IP numbers, 13.248.169.48 and 76.223.54.146

668e.zapd.co, hometownliving.com, puresleep.online plus two other host names have IP numbers in common with hedgeradar.com.

Name Servers

Two name servers handle the delegation for hedgeradar.com: ns3.afternic.com and ns4.afternic.com.

The name server configuration of hedgeradar.com is shared with other domains, for instance qvmo.com, formlead.com, 38.116profile.www.1clickworld.com and two others.

hedgeradar.com partially shares its NS delegation with several other domains, including joinourcult.org, zwsu.com, logiam.com and two others.

These name servers regularly co-occur with the name servers verification-dbgjncnnzmfgmpuki3e6hz.ns101.verify.hn, verification-frsgyqgb387khmr9jzuunx.ns101.verify.hn and bclr8ozfjcs2prxuhhhetc.ns101.verify.hn.

ns3.afternic.com resolves to 97.74.98.65. ns4.afternic.com resolves to 173.201.66.65. Both host names point to a single IP number.