triangularservices.com - dns.ninja
triangularservices.com
com
| DNSSEC | ⚠️ Not signed | ||||||
| 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=1794202836 | ||||||
Same first word
triangularservices.com |
DNS History
17 records (12 active, 5 former)
●NSdns045.c.register.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●NSdns046.b.register.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●NSdns083.d.register.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●NSdns1.register.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●NSdns193.a.register.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●NSdns2.register.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
○NSns37.domaincontrol.com2016-12-20 → 2016-12-20 · 3 obs
○ 2018-05-22 13:01:00
○ 2026-11-09 06:20:38
○NSns38.domaincontrol.com2016-12-20 → 2016-12-20 · 3 obs
○ 2018-05-22 13:01:00
○ 2026-11-09 06:20:38
●MXalt1.aspmx.l.google.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●MXalt2.aspmx.l.google.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●MXalt3.aspmx.l.google.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●MXalt4.aspmx.l.google.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
●MXaspmx.l.google.com2026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
○MXmailstore1.secureserver.net2016-12-20 → 2016-12-20 · 3 obs
○ 2018-05-22 13:01:00
○ 2026-11-09 06:20:38
○MXsmtp.secureserver.net2016-12-20 → 2016-12-20 · 3 obs
○ 2018-05-22 13:01:00
○ 2026-11-09 06:20:38
●A199.34.228.1762026-09-14 → 2026-11-09 · 3 obs
● 2026-09-14 00:20:32
● 2026-11-09 06:20:38
○A50.63.202.492016-12-20 → 2016-12-20 · 3 obs
○ 2018-05-22 13:01:00
○ 2026-11-09 06:20:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, k.gtld-servers.net, e.gtld-servers.net, a.gtld-servers.net... | - |
| triangularservices.com | dns2.register.com, dns1.register.com | 2 records |
✅ Authoritative Response
Server:162.159.27.248
NS records: dns2.register.com, dns1.register.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for triangularservices.com (unsigned zone)
⏱️ Timing
Total: 470ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.34.228.176 |
| NS | 4 | dns045.c.register.com, dns046.b.register.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | dns193.a.register.com root.register.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns2.register.com, dns1.register.com)
Analysis
IP Addresses
triangularservices.com resolves to one IP address: 199.34.228.176.
Name Servers
triangularservices.com has 6 name servers — dns1.register.com, dns2.register.com, dns193.a.register.com and 3 others.
Mail Servers
Mail for triangularservices.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com resolves to 142.251.163.26 and 2607:f8b0:4004:c07::1b.
alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.