trimavencap.com - robtex.com
trimavencap.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=1777478766 | ||||||
Subdomains
mail.trimavencap.com |
Same first word
trimavencap.com |
DNS History
12 records (8 active, 4 former)
●NSns1.netfirms.com2026-04-03 → 2026-04-29 · 3 obs
● 2026-04-03 18:25:26
● 2026-04-29 16:15:28
○NSns1.wix.com2015-05-27 → 2019-01-22 · 4 obs
● 2019-01-22 03:14:10
○ 2026-04-03 18:25:26
○ 2026-04-29 16:15:28
●NSns2.netfirms.com2026-04-03 → 2026-04-29 · 3 obs
● 2026-04-03 18:25:26
● 2026-04-29 16:15:28
○NSns2.wix.com2015-05-27 → 2019-01-22 · 4 obs
● 2019-01-22 03:14:10
○ 2026-04-03 18:25:26
○ 2026-04-29 16:15:28
●MXalt1.aspmx.l.google.com2015-05-27 → 2026-04-29 · 2 obs
● 2026-04-29 16:15:28
●MXalt2.aspmx.l.google.com2015-05-27 → 2026-04-29 · 2 obs
● 2026-04-29 16:15:28
●MXaspmx.l.google.com2015-05-27 → 2026-04-29 · 2 obs
● 2026-04-29 16:15:28
●MXaspmx2.googlemail.com2015-05-27 → 2026-04-29 · 2 obs
● 2026-04-29 16:15:28
●MXaspmx3.googlemail.com2015-05-27 → 2026-04-29 · 2 obs
● 2026-04-29 16:15:28
○MXmail.trimavencap.com2015-05-27 → 2015-10-28 · 4 obs
● 2015-10-28 04:05:28
○ 2016-01-14 12:53:10
○ 2026-04-29 16:15:28
○A23.236.62.1472015-05-27 → 2019-01-22 · 4 obs
● 2019-01-22 03:14:10
○ 2026-04-03 18:25:26
○ 2026-04-29 16:15:28
●A66.96.160.1402026-04-03 → 2026-04-29 · 3 obs
● 2026-04-03 18:25:26
● 2026-04-29 16:15:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| trimavencap.com | ns1.netfirms.com, ns2.netfirms.com | 2 records |
✅ Authoritative Response
Server:65.254.254.157
NS records: ns1.netfirms.com, ns2.netfirms.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for trimavencap.com (unsigned zone)
⏱️ Timing
Total: 160ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.96.160.140 |
| NS | 2 | ns1.netfirms.com, ns2.netfirms.com |
| MX | 5 | ALT2.ASPMX.L.GOOGLE.com (pri: 5), ASPMX.L.GOOGLE.com (pri: 1)... |
| TXT | 2 | v=spf1 ip4:66.96.128.0/18 include:_spf.g, v=DKIM1 k=rsa p=MIGfMA0GCSqGSIb3DQEBAQUA |
| SOA | 1 | ns1.netfirms.com dnsadmin.netfirms.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.netfirms.com, ns2.netfirms.com)
Analysis
Hierarchy
trimavencap.com is a parent of mail.trimavencap.com.
IP Addresses
trimavencap.com points to a single IP address: 66.96.160.140.
Other host names such as ns2.idesignstudio.ca, mx10.rickbell.com, desalalternatives.org, seasonsbahamas.com and mail.trimavencap.com share IP numbers with trimavencap.com.
Name Servers
trimavencap.com is delegated to two name servers: ns1.netfirms.com and ns2.netfirms.com.
trimavencap.com uses the same name server setup as other domains, including mariannethorsen.net, cranfordmoms.com, clouston.ca, shelgreb.com and brifen.ca.
At least part of the name servers for trimavencap.com are shared with other domains, for instance kdcenterprises.ca, dentiste-drummondville.com, finalcutproawards.com, littleburymedicalcentre.com and exachrome.com.
These name servers are commonly used alongside ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.
Hostnames with a single IP
ns1.netfirms.com resolves to: 65.254.254.157.
ns2.netfirms.com resolves to: 66.96.142.145.
Mail Servers
trimavencap.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
trimavencap.com shares at least some mail servers with other domains, for example ns500754.ns500754.ns500742.ns500704.ns500671.ns500671.ns500705.ns500705.ns500688.ns500678.ns500142.lusty(0x736c7574)z.com, ns500731.ns500731.ns500704.ns500704.ns500705.ns500688.ns500705.ns500678.ns500671.ns500291.ns500666.ns500142.lusty(0x736c7574)z.com, ns500742.ns500754.ns500731.ns500754.ns500742.ns500671.ns500704.ns500671.ns500671.ns500291.ns500649.ns500142.lusty(0x736c7574)z.com, ns500693.ns500734.ns500699.ns500734.ns500699.ns500693.ns500699.ns500734.ns500699.ns500699.ns500588.ns500632.ns500588.ns500588.ns500612.ns500588.ns500588.dtrkdll.com and ns500742.ns500671.ns500754.ns500754.ns500742.ns500704.ns500731.ns500705.ns500704.ns500291.ns500688.ns500131.lustychickser.com.
These mail servers are commonly used alongside alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers: aspmx2.googlemail.com points to 2607:f8b0:4023:2801::1a and 192.178.128.27; aspmx3.googlemail.com points to 2a00:1450:400b:c02::1a and 172.253.116.27; aspmx.l.google.com points to 2607:f8b0:4004:c1f::1a and 172.253.122.26; alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1a and 108.177.123.27; alt2.aspmx.l.google.com points to 2a00:1450:4013:c1e::1a and 192.178.213.27.