trinityave.org - dns.ninja
trinityave.org
org
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a2.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | b0.org.afilias-nst.org | ||||||
| NS | b2.org.afilias-nst.org | ||||||
| NS | c0.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | d0.org.afilias-nst.org | ||||||
| SOA | a0.org.afilias-nst.infohostmaster@donuts.email serial=1782747681 | ||||||
Same first word
trinityave.org |
Similar names
DNS History
16 records (8 active, 8 former)
○NSdns010.d.register.com2015-08-17 → 2018-10-10 · 4 obs
● 2018-10-10 05:01:50
○ 2026-06-29 16:18:08
○ 2026-06-29 16:18:12
○NSdns104.c.register.com2015-08-17 → 2018-10-10 · 4 obs
● 2018-10-10 05:01:50
○ 2026-06-29 16:18:08
○ 2026-06-29 16:18:12
○NSdns155.a.register.com2015-08-17 → 2018-10-10 · 4 obs
● 2018-10-10 05:01:50
○ 2026-06-29 16:18:08
○ 2026-06-29 16:18:12
○NSdns218.b.register.com2015-08-17 → 2018-10-10 · 4 obs
● 2018-10-10 05:01:50
○ 2026-06-29 16:18:08
○ 2026-06-29 16:18:12
●NSns29.domaincontrol.com2026-06-29 → 2026-06-29 · 3 obs
● 2026-06-29 16:18:08
● 2026-06-29 16:18:12
●NSns30.domaincontrol.com2026-06-29 → 2026-06-29 · 3 obs
● 2026-06-29 16:18:08
● 2026-06-29 16:18:12
●MXalt1.aspmx.l.google.com2015-08-17 → 2026-06-29 · 2 obs
● 2026-06-29 16:18:12
●MXalt2.aspmx.l.google.com2015-08-17 → 2026-06-29 · 2 obs
● 2026-06-29 16:18:12
●MXalt3.aspmx.l.google.com2026-06-29 → 2026-06-29 · 3 obs
● 2026-06-29 16:18:08
● 2026-06-29 16:18:12
●MXalt4.aspmx.l.google.com2026-06-29 → 2026-06-29 · 3 obs
● 2026-06-29 16:18:08
● 2026-06-29 16:18:12
●MXaspmx.l.google.com2015-08-17 → 2026-06-29 · 2 obs
● 2026-06-29 16:18:12
○MXaspmx2.googlemail.com2015-08-17 → 2018-10-10 · 4 obs
● 2018-10-10 05:01:50
○ 2026-06-29 16:18:08
○ 2026-06-29 16:18:12
○MXaspmx3.googlemail.com2015-08-17 → 2018-10-10 · 4 obs
● 2018-10-10 05:01:50
○ 2026-06-29 16:18:08
○ 2026-06-29 16:18:12
○A50.28.85.692015-08-17 → 2016-07-13 · 4 obs
● 2016-07-13 13:09:42
○ 2016-11-27 19:54:22
○ 2026-06-29 16:18:12
●A52.35.132.1132026-06-29 → 2026-06-29 · 3 obs
● 2026-06-29 16:18:08
● 2026-06-29 16:18:12
○A72.9.145.1862016-11-27 → 2018-10-10 · 5 obs
● 2016-11-27 19:54:22
● 2018-10-10 05:01:50
○ 2026-06-29 16:18:08
○ 2026-06-29 16:18:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| org | b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org | - |
| trinityave.org | ns30.domaincontrol.com, ns29.domaincontrol.com | - |
✅ Authoritative Response
Server:97.74.104.15
NS records: ns30.domaincontrol.com, ns29.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for trinityave.org (unsigned zone)
⏱️ Timing
Total: 311ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.35.132.113 |
| NS | 2 | ns29.domaincontrol.com, ns30.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:dc-aa8e722993._spfm.trini |
| SOA | 1 | ns29.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
trinityave.org directs to one IP number, which is 52.35.132.113.
Among the host names that share IP numbers with trinityave.org are stsent.org, templebaptistkpt.com, kingdomfund.com and two others.
Name Servers
Two name servers handle the delegation for trinityave.org: ns29.domaincontrol.com and ns30.domaincontrol.com.
trinityave.org has the same name server delegation as a number of other domains, such as nuligi.com, mira-butik.com, villaitalia.com and two more.
trinityave.org is at least partially co-delegated on name servers with other domains, such as cotija.biz.
ns29.domaincontrol.com and ns30.domaincontrol.com both carry two IP addresses. The A records for ns29.domaincontrol.com are 97.74.104.15 and 2603:5:2181::f; the A records for ns30.domaincontrol.com are 173.201.72.15 and 2603:5:2281::f.
Mail Servers
trinityave.org has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
trinityave.org shares at least some of its mail servers with other domains — for example ns500754.ns500742.ns500754.ns500671.ns500731.ns500704.ns500731.ns500705.ns500688.ns500704.ns500705.ns500705.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500671.ns500742.ns500731.ns500742.ns500754.ns500742.ns500688.ns500671.ns500705.ns500688.ns500705.ns500671.ns500291.ns500666.ns500142.lusty(0x736c7574)z.com, ns500765.ns500765.ns500699.ns500693.ns500693.ns500693.ns500734.ns500588.ns500588.ns500693.ns500693.ns500588.ns500602.dtrkdll.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to two addresses: 172.253.139.27 and 2607:f8b0:4004:c07::1b.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1b.