echos.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status

echos.com

DNSSEC⚠️ Not signed
A23.92.212.166🇺🇸 DACENTEC-123.92.208.0/20 CUST-NET-9
NSns1.torresdns.com
A23.92.212.162🇺🇸 DACENTEC-123.92.208.0/20 CUST-NET-9
NSns2.torresdns.com
A78.41.207.71🇳🇱 Snel78.41.207.0/24 .com B.V.
PTRdmpro-snel-eu
SOAns1.torresdns.comadmin@echos.com 2026-01-19 #1

com

Same first word

Similar names

DNS History

23 records (3 active, 20 former)

20162017201820192020202120222023202420252026NSns1.torresdns.comns2.torresdns.comns1.echos.comns1.hastydns.comns1.hostresolver.comns2.hastydns.comns2.hostresolver.comA23.92.212.166173.224.126.49173.224.126.58173.224.126.61185.150.189.124185.150.189.166209.126.123.12209.126.123.1323.92.212.16569.162.80.5469.162.80.5569.162.80.6178.41.204.2878.41.207.2078.41.207.2195.211.117.206
NSns1.echos.com2015-11-18 → 2015-11-18 · 4 obs
○ 2015-07-06 03:14:30
● 2015-11-18 02:38:20
○ 2016-02-22 21:50:24
○ 2026-08-17 10:30:20
NSns1.hastydns.com2015-07-06 → 2016-02-22 · 5 obs
● 2015-07-06 03:14:30
○ 2015-11-18 02:38:20
● 2016-02-22 21:50:24
○ 2016-06-14 13:19:26
○ 2026-08-17 10:30:20
NSns1.hostresolver.com2026-06-28 → 2026-06-28 · 4 obs
○ 2016-06-14 13:19:26
● 2026-06-28 09:49:50
○ 2026-07-10 19:04:42
○ 2026-08-17 10:30:20
NSns1.torresdns.com2016-06-14 → 2026-08-17 · 3 obs
○ 2016-02-22 21:50:24
● 2016-06-14 13:19:26
● 2026-08-17 10:30:20
NSns2.hastydns.com2015-07-06 → 2016-02-22 · 5 obs
● 2015-07-06 03:14:30
○ 2015-11-18 02:38:20
● 2016-02-22 21:50:24
○ 2016-06-14 13:19:26
○ 2026-08-17 10:30:20
NSns2.hostresolver.com2026-06-28 → 2026-06-28 · 4 obs
○ 2016-06-14 13:19:26
● 2026-06-28 09:49:50
○ 2026-07-10 19:04:42
○ 2026-08-17 10:30:20
NSns2.torresdns.com2016-06-14 → 2026-08-17 · 3 obs
○ 2016-02-22 21:50:24
● 2016-06-14 13:19:26
● 2026-08-17 10:30:20
A173.224.126.492026-02-16 → 2026-02-26 · 6 obs
○ 2017-06-09 03:45:40
● 2026-02-16 14:52:50
○ 2026-02-24 11:55:02
● 2026-02-26 17:17:42
○ 2026-03-22 01:10:10
○ 2026-08-17 10:30:20
A173.224.126.582026-03-23 → 2026-03-23 · 4 obs
○ 2026-03-22 01:10:10
● 2026-03-23 14:10:36
○ 2026-03-24 14:12:38
○ 2026-08-17 10:30:20
A173.224.126.612026-02-24 → 2026-03-24 · 8 obs
○ 2026-02-16 14:52:50
● 2026-02-24 11:55:02
○ 2026-02-26 17:17:42
● 2026-03-22 01:10:10
○ 2026-03-23 14:10:36
● 2026-03-24 14:12:38
○ 2026-05-31 00:30:12
○ 2026-08-17 10:30:20
A185.150.189.1242026-07-01 → 2026-07-01 · 4 obs
○ 2026-06-28 09:49:50
● 2026-07-01 15:17:26
○ 2026-08-04 12:55:52
○ 2026-08-17 10:30:20
A185.150.189.1662026-06-26 → 2026-06-26 · 4 obs
○ 2026-06-21 03:52:04
● 2026-06-26 19:15:04
○ 2026-06-28 09:49:50
○ 2026-08-17 10:30:20
A209.126.123.122016-06-14 → 2016-06-14 · 4 obs
○ 2016-02-22 21:50:24
● 2016-06-14 13:19:26
○ 2017-01-29 21:30:20
○ 2026-08-17 10:30:20
A209.126.123.132017-06-09 → 2017-06-09 · 4 obs
○ 2017-01-29 21:30:20
● 2017-06-09 03:45:40
○ 2026-02-16 14:52:50
○ 2026-08-17 10:30:20
A23.92.212.1652026-08-04 → 2026-08-04 · 4 obs
○ 2026-07-01 15:17:26
● 2026-08-04 12:55:52
○ 2026-08-07 19:50:36
○ 2026-08-17 10:30:20
A23.92.212.1662026-08-07 → 2026-08-17 · 3 obs
○ 2026-08-04 12:55:52
● 2026-08-07 19:50:36
● 2026-08-17 10:30:20
A69.162.80.542015-07-06 → 2015-07-06 · 3 obs
● 2015-07-06 03:14:30
○ 2015-11-18 02:38:20
○ 2026-08-17 10:30:20
A69.162.80.552015-11-18 → 2015-11-18 · 4 obs
○ 2015-07-06 03:14:30
● 2015-11-18 02:38:20
○ 2016-02-22 21:50:24
○ 2026-08-17 10:30:20
A69.162.80.612016-02-22 → 2016-02-22 · 4 obs
○ 2015-11-18 02:38:20
● 2016-02-22 21:50:24
○ 2016-06-14 13:19:26
○ 2026-08-17 10:30:20
A78.41.204.282017-01-29 → 2017-06-09 · 5 obs
○ 2016-06-14 13:19:26
● 2017-01-29 21:30:20
● 2017-06-09 03:45:40
○ 2026-02-16 14:52:50
○ 2026-08-17 10:30:20
A78.41.207.202026-05-31 → 2026-05-31 · 4 obs
○ 2026-03-24 14:12:38
● 2026-05-31 00:30:12
○ 2026-06-21 03:52:04
○ 2026-08-17 10:30:20
A78.41.207.212026-06-28 → 2026-06-28 · 4 obs
○ 2026-06-26 19:15:04
● 2026-06-28 09:49:50
○ 2026-07-01 15:17:26
○ 2026-08-17 10:30:20
A95.211.117.2062015-07-06 → 2015-07-06 · 3 obs
● 2015-07-06 03:14:30
○ 2017-06-09 03:45:40
○ 2026-08-17 10:30:20

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
echos.comns1.torresdns.com, ns2.torresdns.com2 records

✅ Authoritative Response

Server:23.92.212.162

NS records: ns1.torresdns.com, ns2.torresdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for echos.com (unsigned zone)

⏱️ Timing

Total: 294ms | Queries: -

📄 Records

TypeCountSample Data
A178.41.207.27
NS2ns1.torresdns.com, ns2.torresdns.com
TXT1dbg: src: ds, acme: false
SOA1ns1.torresdns.com admin.echos.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.torresdns.com, ns2.torresdns.com)

Analysis

IP Addresses

echos.com points to a single IP number: 23.92.212.166.

Additional host names — ns3.root.ns1.ns4.blackry.com, fr.youtubetomp3.org, ancesrty.com and two others — share IP numbers with echos.com.

Name Servers

Two name servers handle the delegation for echos.com: ns1.torresdns.com and ns2.torresdns.com.

echos.com shares its name server setup with other domains, including thesarous.com, bruneiair.com, wndows.com and two others.

echos.com shares at least some of its name servers with other domains, including rbxrocks.com, sciecedirect.com, tripadvisoe.com and two others.

These name servers are frequently paired with the name servers ns1.hostresolver.com and ns2.hostresolver.com.

ns1.torresdns.com and ns2.torresdns.com each resolve to one IP number: ns1.torresdns.com points to 23.92.212.162 and ns2.torresdns.com points to 78.41.207.71.