Analysis performed on Aug 31, 2025
This is a comprehensive technical analysis of ecopromx.com performed on August 31, 2025. The analysis includes DNS configuration, server information, WHOIS data, and HTTP response details.
Quick Navigation
🤖 AI Analysis Summary
{
"status": "insufficient_content",
"reason": "Site content not available due to fetch error"
}
🌐 Domain Information
The domain ecopromx.com was registered on July 30, 2025, indicating it is currently less than a year old. It is registered until July 30, 2035, with a status that prohibits client deletion, renewal, transfer, and updates. The registrar is GoDaddy.com, LLC, and the domain is configured with nameservers NS05.DOMAINCONTROL.COM and NS06.DOMAINCONTROL.COM.
WHOIS Registration Details
| Registrar | GoDaddy.com, LLC |
| Registration Date | 2025-07-30 |
| Expiration Date | 2035-07-30 |
| Name Servers | NS05.DOMAINCONTROL.COM NS06.DOMAINCONTROL.COM |
⚙️ Technical Data
The DNS configuration for ecopromx.com includes multiple A records pointing to two IP addresses and several MX records for email routing through Google services. Security implementation is currently not verified, as the HTTP status indicates a connection timeout, suggesting that SSL/HTTPS configuration cannot be assessed. The technology stack and server information are not discernible due to the lack of successful HTTP response data.
DNS Records
A Records
| Host | IP Address | TTL |
|---|---|---|
| @ | 3.33.251.168 | 3599 |
MX Records
| Host | Mail Server | Priority | TTL |
|---|---|---|---|
| ecopromx.com | alt2.aspmx.l.google.com | 5 | 3599 |
| ecopromx.com | aspmx.l.google.com | 1 | 3599 |
| ecopromx.com | alt3.aspmx.l.google.com | 10 | 3599 |
| ecopromx.com | alt1.aspmx.l.google.com | 5 | 3599 |
| ecopromx.com | alt4.aspmx.l.google.com | 10 | 3599 |
NS Records
| Host | Target | TTL |
|---|---|---|
| ecopromx.com | ns06.domaincontrol.com | 3599 |
| ecopromx.com | ns05.domaincontrol.com | 3599 |
HTTP Status Information
| Redirect Chain | |
| Response Time | 0 ms |
| Error | ❌ Connection timed out after 10002 milliseconds |