e2ro.com - robtex.com

e2ro.com

com

πŸ“ˆ Tranco rank: #529
e2ro.com - Tranco Rank (30d: ↑+42)510520540560580600605Jun 14Jun 23Jul 2Jul 11Jul 20Rank#571#529

e2ro.com

Overview

e2ro.com appears to be a defensive domain registration owned by or associated with eero, the mesh WiFi company now owned by Amazon. The domain name is a common typo of "eero" (with "2" replacing the second "e"), and is likely held to protect the eero brand and redirect users who mistype the URL.

Domain Details

  • Registered: May 26, 2015
  • Expires: October 12, 2033
  • Registrar: Amazon Registrar, Inc.
  • Status: Locked (client delete/transfer/update prohibited)
  • Nameservers: AWS DNS infrastructure

The domain does not currently resolve to a live website. Registrant information is protected through an identity protection service based in the UK.

About eero (Parent Brand)

eero is a San Francisco-based company that pioneered consumer mesh WiFi systems. Key facts:

  • Founded: 2014
  • Acquired by Amazon: 2019
  • Products: Mesh WiFi routers (eero Pro 7, eero PoE 7), eero Plus subscription service
  • Scale: 20M+ devices deployed across 27+ countries
  • Ratings: 95,000+ Amazon reviews with 4.5-star average

eero's products are known for easy setup, automatic updates, and integrated security features including parental controls, ad blocking, and VPN services.

Subdomains

Same first word

Similar names

DNS History

16 records (4 active, 12 former)

20162017201820192020202120222023202420252026NSns-1269.awsdns-30.orgns-1903.awsdns-45.co.ukns-401.awsdns-50.comns-573.awsdns-07.netdns1.registrar-servers.comdns2.registrar-servers.comdns3.registrar-servers.comdns4.registrar-servers.comdns5.registrar-servers.comMXeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA162.255.119.250162.255.119.251
β—‹NSdns1.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹NSdns2.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹NSdns3.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹NSdns4.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹NSdns5.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
●NSns-1269.awsdns-30.org2016-04-24 β†’ 2026-07-22 Β· 3 obs
β—‹ 2015-12-08 20:06:56
● 2016-04-24 06:37:44
● 2026-07-22 19:40:52
●NSns-1903.awsdns-45.co.uk2016-04-24 β†’ 2026-07-22 Β· 3 obs
β—‹ 2015-12-08 20:06:56
● 2016-04-24 06:37:44
● 2026-07-22 19:40:52
●NSns-401.awsdns-50.com2016-04-24 β†’ 2026-07-22 Β· 3 obs
β—‹ 2015-12-08 20:06:56
● 2016-04-24 06:37:44
● 2026-07-22 19:40:52
●NSns-573.awsdns-07.net2016-04-24 β†’ 2026-07-22 Β· 3 obs
β—‹ 2015-12-08 20:06:56
● 2016-04-24 06:37:44
● 2026-07-22 19:40:52
β—‹MXeforward1.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹MXeforward2.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹MXeforward3.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹MXeforward4.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹MXeforward5.registrar-servers.com2015-08-26 β†’ 2015-12-08 Β· 4 obs
● 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52
β—‹A162.255.119.2502015-08-26 β†’ 2015-08-26 Β· 3 obs
● 2015-08-26 00:25:54
β—‹ 2015-12-08 20:06:56
β—‹ 2026-07-22 19:40:52
β—‹A162.255.119.2512015-12-08 β†’ 2015-12-08 Β· 4 obs
β—‹ 2015-08-26 00:25:54
● 2015-12-08 20:06:56
β—‹ 2016-04-24 06:37:44
β—‹ 2026-07-22 19:40:52

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
e2ro.comns-573.awsdns-07.net, ns-401.awsdns-50.com, ns-1269.awsdns-30.org, ns-1903.awsdns-45.co.uk2 records

βœ… Authoritative Response

Server:205.251.193.145

NS records: ns-573.awsdns-07.net, ns-401.awsdns-50.com, ns-1269.awsdns-30.org, ns-1903.awsdns-45.co.uk

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for e2ro.com (unsigned zone)

⏱️ Timing

Total: 1179ms | Queries: -

πŸ“„ Records

TypeCountSample Data
NS4ns-1269.awsdns-30.org, ns-1903.awsdns-45.co.uk...
TXT1v=spf1 -all
SOA1ns-1269.awsdns-30.org awsdns-hostmaster.

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-401.awsdns-50.com, ns-401.awsdns-50.com)

Analysis

Hierarchy

e2ro.com serves as parent to ookla-speedtests.e2ro.com, wds.e2ro.com, api-admin.e2ro.com, api-user.e2ro.com, admin.e2ro.com along with a few other host names.

Name Servers

Four name servers handle the delegation for e2ro.com: ns-401.awsdns-50.com, ns-573.awsdns-07.net, ns-1269.awsdns-30.org and ns-1903.awsdns-45.co.uk.

e2ro.com has at least partial name server overlap with other domains, such as 365gum.cn, luxcrave.com, lmode.jp and two others.

ns-401.awsdns-50.com, ns-573.awsdns-07.net, ns-1269.awsdns-30.org and ns-1903.awsdns-45.co.uk all point to exactly two IP numbers each: ns-401.awsdns-50.com β†’ 205.251.193.145 and 2600:9000:5301:9100::1; ns-573.awsdns-07.net β†’ 205.251.194.61 and 2600:9000:5302:3d00::1; ns-1269.awsdns-30.org β†’ 205.251.196.245 and 2600:9000:5304:f500::1; ns-1903.awsdns-45.co.uk β†’ 205.251.199.111 and 2600:9000:5307:6f00::1.