trafficcommand.com - dns.ninja
trafficcommand.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns1.namefind.com ⭐ | ||||||
| A | 97.74.99.64🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.namefind.com | ||||||
| NS | ns2.namefind.com | ||||||
| A | 173.201.67.64🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.namefind.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.namefind.comdns@jomax.net 2023-03-15 #0 | ||||||
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=1793638436 | ||||||
Same first word
trafficcommand.com |
Similar names
DNS History
18 records (4 active, 14 former)
○NSbuy.internettraffic.com2015-10-31 → 2016-06-30 · 5 obs
○ 2015-06-19 22:18:54
● 2015-10-31 21:22:42
● 2016-06-30 10:21:06
○ 2017-02-15 16:39:24
○ 2026-11-02 17:09:36
● 2015-10-31 21:22:42
● 2016-06-30 10:21:06
○ 2017-02-15 16:39:24
○ 2026-11-02 17:09:36
○NSns1.mark.com2015-06-19 → 2015-06-19 · 3 obs
● 2015-06-19 22:18:54
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
●NSns1.namefind.com2020-01-19 → 2026-11-02 · 3 obs
○ 2017-02-15 16:39:24
● 2020-01-19 08:41:08
● 2026-11-02 17:09:36
● 2020-01-19 08:41:08
● 2026-11-02 17:09:36
○NSns1.uniregistrymarket.link2017-02-15 → 2017-02-15 · 4 obs
○ 2016-06-30 10:21:06
● 2017-02-15 16:39:24
○ 2020-01-19 08:41:08
○ 2026-11-02 17:09:36
● 2017-02-15 16:39:24
○ 2020-01-19 08:41:08
○ 2026-11-02 17:09:36
○NSns2.mark.com2015-06-19 → 2015-06-19 · 3 obs
● 2015-06-19 22:18:54
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
●NSns2.namefind.com2020-01-19 → 2026-11-02 · 3 obs
○ 2017-02-15 16:39:24
● 2020-01-19 08:41:08
● 2026-11-02 17:09:36
● 2020-01-19 08:41:08
● 2026-11-02 17:09:36
○NSns2.uniregistrymarket.link2017-02-15 → 2017-02-15 · 4 obs
○ 2016-06-30 10:21:06
● 2017-02-15 16:39:24
○ 2020-01-19 08:41:08
○ 2026-11-02 17:09:36
● 2017-02-15 16:39:24
○ 2020-01-19 08:41:08
○ 2026-11-02 17:09:36
○NSsell.internettraffic.com2015-10-31 → 2016-06-30 · 5 obs
○ 2015-06-19 22:18:54
● 2015-10-31 21:22:42
● 2016-06-30 10:21:06
○ 2017-02-15 16:39:24
○ 2026-11-02 17:09:36
● 2015-10-31 21:22:42
● 2016-06-30 10:21:06
○ 2017-02-15 16:39:24
○ 2026-11-02 17:09:36
○MXnullmx.trafficcommand.com2015-06-19 → 2015-06-19 · 3 obs
● 2015-06-19 22:18:54
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
●A13.248.169.482026-08-20 → 2026-11-02 · 3 obs
○ 2020-01-19 08:41:08
● 2026-08-20 17:55:02
● 2026-11-02 17:09:36
● 2026-08-20 17:55:02
● 2026-11-02 17:09:36
○A2406:da00:ff00::36c5:f8012015-06-19 → 2015-06-19 · 3 obs
● 2015-06-19 22:18:54
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○A2406:da00:ff00::36f3:64c72015-06-19 → 2015-06-19 · 3 obs
● 2015-06-19 22:18:54
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○A35.186.238.1012020-01-19 → 2020-01-19 · 4 obs
○ 2017-02-15 16:39:24
● 2020-01-19 08:41:08
○ 2026-08-20 17:55:02
○ 2026-11-02 17:09:36
● 2020-01-19 08:41:08
○ 2026-08-20 17:55:02
○ 2026-11-02 17:09:36
○A54.197.248.12015-06-19 → 2015-06-19 · 3 obs
● 2015-06-19 22:18:54
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○A54.243.100.1992015-06-19 → 2015-06-19 · 3 obs
● 2015-06-19 22:18:54
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○ 2015-10-31 21:22:42
○ 2026-11-02 17:09:36
○A69.172.201.1532016-06-30 → 2017-02-15 · 5 obs
○ 2016-03-01 17:00:06
● 2016-06-30 10:21:06
● 2017-02-15 16:39:24
○ 2020-01-19 08:41:08
○ 2026-11-02 17:09:36
● 2016-06-30 10:21:06
● 2017-02-15 16:39:24
○ 2020-01-19 08:41:08
○ 2026-11-02 17:09:36
○A69.172.201.2082015-10-31 → 2016-03-01 · 5 obs
○ 2015-06-19 22:18:54
● 2015-10-31 21:22:42
● 2016-03-01 17:00:06
○ 2016-06-30 10:21:06
○ 2026-11-02 17:09:36
● 2015-10-31 21:22:42
● 2016-03-01 17:00:06
○ 2016-06-30 10:21:06
○ 2026-11-02 17:09:36
●A76.223.54.1462026-08-20 → 2026-11-02 · 3 obs
○ 2020-01-19 08:41:08
● 2026-08-20 17:55:02
● 2026-11-02 17:09:36
● 2026-08-20 17:55:02
● 2026-11-02 17:09:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| trafficcommand.com | ns2.namefind.com, ns1.namefind.com | 2 records |
✅ Authoritative Response
Server:173.201.67.64
NS records: ns2.namefind.com, ns1.namefind.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for trafficcommand.com (unsigned zone)
⏱️ Timing
Total: 630ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 13.248.169.48, 76.223.54.146 |
| NS | 2 | ns1.namefind.com, ns2.namefind.com |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.namefind.com dns.jomax.net |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.namefind.com, ns1.namefind.com)
Analysis
IP Addresses
trafficcommand.com directs to two IP numbers, 13.248.169.48 and 76.223.54.146
Name Servers
The NS records for trafficcommand.com delegate to ns1.namefind.com and ns2.namefind.com.
The host names ns1.namefind.com and ns2.namefind.com each point to one IP number: ns1.namefind.com points to 97.74.99.64. ns2.namefind.com points to 173.201.67.64.