trianglefencing.com - dns.ninja
trianglefencing.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=1782384120 | ||||||
Same first word
trianglefencing.com |
DNS History
11 records (8 active, 3 former)
○NSns1.namebrightdns.com2017-11-03 → 2017-11-03 · 3 obs
○ 2026-05-10 13:30:38
○ 2026-06-25 10:51:44
○NSns2.namebrightdns.com2017-11-03 → 2017-11-03 · 3 obs
○ 2026-05-10 13:30:38
○ 2026-06-25 10:51:44
●NSns61.domaincontrol.com2026-05-10 → 2026-06-25 · 3 obs
● 2026-05-10 13:30:38
● 2026-06-25 10:51:44
●NSns62.domaincontrol.com2026-05-10 → 2026-06-25 · 3 obs
● 2026-05-10 13:30:38
● 2026-06-25 10:51:44
●MXalt1.aspmx.l.google.com2026-05-10 → 2026-06-25 · 2 obs
● 2026-06-25 10:51:44
●MXalt2.aspmx.l.google.com2026-05-10 → 2026-06-25 · 2 obs
● 2026-06-25 10:51:44
●MXalt3.aspmx.l.google.com2026-05-10 → 2026-06-25 · 2 obs
● 2026-06-25 10:51:44
●MXalt4.aspmx.l.google.com2026-05-10 → 2026-06-25 · 2 obs
● 2026-06-25 10:51:44
●MXaspmx.l.google.com2026-05-10 → 2026-06-25 · 2 obs
● 2026-06-25 10:51:44
●A75.2.60.52026-05-10 → 2026-06-25 · 2 obs
● 2026-06-25 10:51:44
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-11-03 → 2017-11-03 · 3 obs
○ 2026-05-10 13:30:38
○ 2026-06-25 10:51:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| trianglefencing.com | ns61.domaincontrol.com, ns62.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.69.32
NS records: ns61.domaincontrol.com, ns62.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for trianglefencing.com (unsigned zone)
⏱️ Timing
Total: 148ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.2.60.5 |
| NS | 2 | ns61.domaincontrol.com, ns62.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=g-6fn4FR7-bJgYp, v=spf1 include:dc-aa8e722993._spfm.trian |
| SOA | 1 | ns61.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns61.domaincontrol.com, ns61.domaincontrol.com, ns62.domaincontrol.com...)
Analysis
IP Addresses
trianglefencing.com resolves to one IP address: 75.2.60.5.
novafield.com, www.nuclea.ch, eszakzemplen.hu and two other host names share IP numbers with trianglefencing.com.
Name Servers
Two name servers handle the delegation for trianglefencing.com: ns61.domaincontrol.com and ns62.domaincontrol.com.
trianglefencing.com uses the same name servers as several other domains — among them logicalbalance.com, b2borderpro.com, byepin.net and two more.
ns61.domaincontrol.com and ns62.domaincontrol.com both carry two IP addresses. The A records for ns61.domaincontrol.com are 97.74.101.32 and 2603:5:2153::20; the A records for ns62.domaincontrol.com are 173.201.69.32 and 2603:5:2253::20.
Mail Servers
trianglefencing.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
trianglefencing.com has at least partial mail server overlap with other domains such as sugun.mobi, 2mlpharmacare.com, purposedrivenpublishing.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com resolves to two addresses: 192.178.155.26 and 2607:f8b0:4004:c08::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
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::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.