tri.church - robtex.com
tri.church
church
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | v0n0.nic.church ⭐ | ||||||
| NS | v0n1.nic.church | ||||||
| NS | v0n2.nic.church | ||||||
| NS | v0n3.nic.church | ||||||
| NS | v2n0.nic.church | ||||||
| NS | v2n1.nic.church | ||||||
| SOA | v0n0.nic.churchhostmaster@donuts.email serial=1776990768 | ||||||
Same first word
Similar names
DNS History
8 records (8 active, 0 former)
●NSns1.bluehost.com2026-04-20 → 2026-04-24 · 2 obs
● 2026-04-24 01:07:22
●NSns2.bluehost.com2026-04-20 → 2026-04-24 · 2 obs
● 2026-04-24 01:07:22
●MXalt1.aspmx.l.google.com2026-04-20 → 2026-04-24 · 2 obs
● 2026-04-24 01:07:22
●MXalt2.aspmx.l.google.com2026-04-20 → 2026-04-24 · 2 obs
● 2026-04-24 01:07:22
●MXalt3.aspmx.l.google.com2026-04-20 → 2026-04-24 · 2 obs
● 2026-04-24 01:07:22
●MXalt4.aspmx.l.google.com2026-04-20 → 2026-04-24 · 2 obs
● 2026-04-24 01:07:22
●MXaspmx.l.google.com2026-04-20 → 2026-04-24 · 2 obs
● 2026-04-24 01:07:22
●A173.254.105.2182026-04-20 → 2026-04-24 · 2 obs
● 2026-04-24 01:07:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| church | v0n2.nic.church, v2n1.nic.church, v2n0.nic.church, v0n1.nic.church... | 12 records |
| tri.church | ns1.bluehost.com, ns2.bluehost.com | - |
✅ Authoritative Response
Server:162.159.24.80
NS records: ns1.bluehost.com, ns2.bluehost.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tri.church (unsigned zone)
⏱️ Timing
Total: 698ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 173.254.105.218 |
| NS | 2 | ns2.bluehost.com, ns1.bluehost.com |
| MX | 5 | alt3.aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 +a +mx +ip4:50.87.221.44 +ip4:173, google-site-verification=vwy7_SOAcS5qU1g |
| SOA | 1 | ns1.bluehost.com root.box2232.bluehost.c |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (v2n1.nic.church, v2n0.nic.church, v0n3.nic.church...)
Analysis
IP Addresses
tri.church resolves to one IP number: 173.254.105.218.
Other host names, for instance 173-254-105-218.unifiedlayer.com, share IP numbers with tri.church.
Name Servers
tri.church is delegated to two name servers ns1.bluehost.com and ns2.bluehost.com.
tri.church shares the same name server setup as other domains, for instance dpcsoftware.com, cameron-can.com, thesmittens.com, catherinehay.com and handleyrealty.com.
tri.church shares name servers with other domains at least partially, for example dragonsandmermaids.com and callb4ucut.com.
Host names with one IP number:
ns1.bluehost.com points to 162.159.24.80
ns2.bluehost.com points to 162.159.25.175
Mail Servers
tri.church is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
tri.church shares some mail servers with other domains, at least partially, for instance ns500742.ns500742.ns500754.ns500742.ns500731.ns500754.ns500688.ns500671.ns500704.ns500671.ns500704.ns500678.ns500671.lustychickser.com, ns500698.ns500698.ns500758.ns500758.ns500735.ns500735.ns500698.ns500735.ns500736.ns500735.ns500698.ns500652.ns500576.ns500576.trackreceptor.com, ns500758.ns500698.ns500759.ns500698.ns500698.ns500698.ns500735.ns500735.ns500698.ns500698.ns500576.ns500708.ns500576.ns500698.ns500708.ns500619.ns500652.trackreceptor.com, tumac.eu and ns500671.ns500742.ns500671.ns500731.ns500742.ns500671.ns500704.ns500671.ns500671.ns500688.ns500671.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com.
these mail servers are often used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4004:c06::1a and 64.233.180.26
alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1a and 108.177.123.26
alt2.aspmx.l.google.com points to 2a00:1450:400b:c02::1a and 172.253.116.27
alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1b and 192.178.223.26
alt4.aspmx.l.google.com points to 2607:f8b0:4001:c70::1b and 192.178.209.27