trident-security.com - dns.ninja
trident-security.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=1781230748 | ||||||
Subdomains
server.trident-security.com |
Same first word
trident-security.com |
DNS History
15 records (9 active, 6 former)
●NSns-1306.awsdns-35.org2026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
●NSns-1621.awsdns-10.co.uk2026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
●NSns-303.awsdns-37.com2026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
●NSns-567.awsdns-06.net2026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
○NSns67.domaincontrol.com2015-08-14 → 2017-03-26 · 4 obs
● 2017-03-26 13:27:52
○ 2026-02-19 12:12:52
○ 2026-06-12 02:31:40
○NSns68.domaincontrol.com2015-08-14 → 2017-03-26 · 4 obs
● 2017-03-26 13:27:52
○ 2026-02-19 12:12:52
○ 2026-06-12 02:31:40
●MXesa1.hc358-86.ca.iphmx.com2026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
●MXesa2.hc358-86.ca.iphmx.com2026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
●MXesa3.hc358-86.ca.iphmx.com2026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
●MXesa4.hc358-86.ca.iphmx.com2026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
○MXtrident-security.com.1.0001.arsmtp.com2015-08-14 → 2017-03-26 · 4 obs
● 2017-03-26 13:27:52
○ 2026-02-19 12:12:52
○ 2026-06-12 02:31:40
○MXtrident-security.com.2.0001.arsmtp.com2015-08-14 → 2017-03-26 · 4 obs
● 2017-03-26 13:27:52
○ 2026-02-19 12:12:52
○ 2026-06-12 02:31:40
○A184.168.233.12015-08-14 → 2016-07-17 · 4 obs
● 2016-07-17 15:21:02
○ 2017-03-26 13:27:52
○ 2026-06-12 02:31:40
●A50.16.214.1632026-02-19 → 2026-06-12 · 3 obs
● 2026-02-19 12:12:52
● 2026-06-12 02:31:40
○A50.62.198.702017-03-26 → 2017-03-26 · 4 obs
● 2017-03-26 13:27:52
○ 2026-02-19 12:12:52
○ 2026-06-12 02:31:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, k.gtld-servers.net, j.gtld-servers.net, d.gtld-servers.net... | - |
| trident-security.com | ns-567.awsdns-06.net, ns-303.awsdns-37.com, ns-1621.awsdns-10.co.uk, ns-1306.awsdns-35.org | 2 records |
✅ Authoritative Response
Server:205.251.193.47
NS records: ns-567.awsdns-06.net, ns-303.awsdns-37.com, ns-1621.awsdns-10.co.uk, ns-1306.awsdns-35.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for trident-security.com (unsigned zone)
⏱️ Timing
Total: 500ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 50.16.214.163 |
| NS | 4 | ns-1306.awsdns-35.org, ns-1621.awsdns-10.co.uk... |
| MX | 4 | esa1.hc358-86.ca.iphmx.com (pri: 10), esa2.hc358-86.ca.iphmx.com (pri: 10)... |
| TXT | 2 | MS=ms93943680, v=spf1 -all |
| SOA | 1 | ns-567.awsdns-06.net awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-303.awsdns-37.com, ns-303.awsdns-37.com)
Analysis
Hierarchy
The domain server.trident-security.com falls under the parent trident-security.com.
IP Addresses
trident-security.com points to a single IP number: 50.16.214.163.
Additional host names — www.whelansecurity.com, cpssecurity.com, unitedamericansecurity.com and two others — share IP numbers with trident-security.com.
Name Servers
trident-security.com is delegated to four name servers, ns-303.awsdns-37.com, ns-567.awsdns-06.net, ns-1306.awsdns-35.org and ns-1621.awsdns-10.co.uk.
At least some of trident-security.com's name servers are shared with other domains, for example onesparephotoshoot.com, ticketsms.de, partslocator.com.au and two more.
It is common for these name servers to be used in conjunction with the name servers ns-1716.awsdns-22.co.uk, ns-204.awsdns-25.com and ns-761.awsdns-31.net.
Four hostnames, each resolving to a pair of IP addresses: ns-303.awsdns-37.com directs to 205.251.193.47 and 2600:9000:5301:2f00::1; ns-567.awsdns-06.net directs to 205.251.194.55 and 2600:9000:5302:3700::1; ns-1306.awsdns-35.org directs to 205.251.197.26 and 2600:9000:5305:1a00::1; ns-1621.awsdns-10.co.uk directs to 205.251.198.85 and 2600:9000:5306:5500::1.
Mail Servers
trident-security.com is handled by four mail servers, esa1.hc358-86.ca.iphmx.com, esa2.hc358-86.ca.iphmx.com, esa3.hc358-86.ca.iphmx.com and esa4.hc358-86.ca.iphmx.com.
trident-security.com shares mail servers — at least in part — with other domains, including garda.ca, protectrondrummond.com, alarmeprudential.ca and two others.
esa1.hc358-86.ca.iphmx.com, esa2.hc358-86.ca.iphmx.com, esa3.hc358-86.ca.iphmx.com and esa4.hc358-86.ca.iphmx.com each resolve to one IP address: esa1.hc358-86.ca.iphmx.com resolves to 216.71.135.12, esa2.hc358-86.ca.iphmx.com resolves to 216.71.135.13, esa3.hc358-86.ca.iphmx.com resolves to 216.71.130.180 and esa4.hc358-86.ca.iphmx.com resolves to 216.71.130.182.