securitydirector.com - dns.ninja
securitydirector.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=1786150844 | ||||||
Same first word
securitydirector.com |
DNS History
11 records (9 active, 2 former)
●NSns21.domaincontrol.com2015-08-10 → 2026-08-08 · 2 obs
● 2026-08-08 01:21:34
●NSns22.domaincontrol.com2015-08-10 → 2026-08-08 · 2 obs
● 2026-08-08 01:21:34
●MXalt1.aspmx.l.google.com2015-08-10 → 2026-08-08 · 2 obs
● 2026-08-08 01:21:34
●MXalt2.aspmx.l.google.com2015-08-10 → 2026-08-08 · 2 obs
● 2026-08-08 01:21:34
●MXaspmx.l.google.com2015-08-10 → 2026-08-08 · 2 obs
● 2026-08-08 01:21:34
●MXaspmx2.googlemail.com2015-08-10 → 2026-08-08 · 2 obs
● 2026-08-08 01:21:34
●MXaspmx3.googlemail.com2015-08-10 → 2026-08-08 · 2 obs
● 2026-08-08 01:21:34
●A15.197.225.1282026-05-12 → 2026-08-08 · 3 obs
● 2026-05-12 15:08:20
● 2026-08-08 01:21:34
○A184.168.221.102016-07-15 → 2017-05-23 · 5 obs
● 2016-07-15 16:40:46
● 2017-05-23 09:26:54
○ 2026-05-12 15:08:20
○ 2026-08-08 01:21:34
●A3.33.251.1682026-05-12 → 2026-08-08 · 3 obs
● 2026-05-12 15:08:20
● 2026-08-08 01:21:34
○A50.63.202.402015-08-10 → 2016-03-11 · 4 obs
● 2016-03-11 21:34:08
○ 2016-07-15 16:40:46
○ 2026-08-08 01:21:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| securitydirector.com | ns21.domaincontrol.com, ns22.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.68.11
NS records: ns21.domaincontrol.com, ns22.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for securitydirector.com (unsigned zone)
⏱️ Timing
Total: 150ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns21.domaincontrol.com, ns22.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 mx mx:v=spf1 include:_spf.google. |
| SOA | 1 | ns21.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns21.domaincontrol.com, ns21.domaincontrol.com, ns22.domaincontrol.com...)
Analysis
IP Addresses
securitydirector.com resolves to the IP addresses 3.33.251.168 and 15.197.225.128
Additional host names — sqasquaredhub.com, thehaguemarriott.com, encoreconcert.net and two others — share IP numbers with securitydirector.com.
Name Servers
securitydirector.com has two authoritative name servers — ns21.domaincontrol.com and ns22.domaincontrol.com.
securitydirector.com shares its name server setup with other domains, including fakeamericans.com, safache.com, northlightarchitects.com and two others.
Both ns21.domaincontrol.com and ns22.domaincontrol.com have two IP addresses each. ns21.domaincontrol.com resolves to 97.74.100.11 and 2603:5:2141::b; ns22.domaincontrol.com resolves to 173.201.68.11 and 2603:5:2241::b.
Mail Servers
securitydirector.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
securitydirector.com shares mail servers — at least in part — with other domains, including michelleriveramusic.com, ns500699.ns500699.ns500734.ns500734.ns500699.ns500699.ns500734.ns500734.ns500588.ns500588.ns500699.ns500588.ns500632.ns500588.ns500588.dtrkdll.com, ns500731.ns500742.ns500671.ns500671.ns500704.ns500731.ns500671.ns500671.ns500671.ns500291.ns500291.lustychickser.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com resolves to 142.251.163.27 and 2607:f8b0:4004:c21::1b.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c0f::1a IP addresses.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 108.177.123.26 IP addresses.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 2a00:1450:400b:c02::1a IP addresses.