techtrojan.com - dns.ninja
techtrojan.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.56.33.8🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix | ||||||
| PTR | ec2-13-56-33-8.us-west-1.compute.amazonaws.com | ||||||
| NS | ns1.brandbucket.com ⭐ | ||||||
| A | 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS | ||||||
| A | 54.241.53.41🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix | ||||||
| PTR | ec2-54-241-53-41.us-west-1.compute.amazonaws.com | ||||||
| NS | ns2.brandbucket.com | ||||||
| A | 2600:1f16:54:8701:4012:7e34:5c5f:95a8🇺🇸 Amazon2600:1f16::/38 AMAZON AWS | ||||||
| A | 18.221.52.246🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix | ||||||
| PTR | ec2-18-221-52-246.us-east-2.compute.amazonaws.com | ||||||
| TXT | afternic-verification-cvgUQU8SkLxsjXcPBSk2CM | ||||||
| TXT | 27aab5373841b85aab94982ee19ab62f96481ed6 | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.brandbucket.commail@techtrojan.com 2024-03-05 #2 | ||||||
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=1781651580 | ||||||
Same first word
techtrojan.com |
Similar names
DNS History
24 records (3 active, 21 former)
○NSdns1.name-services.com2017-03-14 → 2017-03-14 · 4 obs
○ 2016-07-05 05:44:14
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
○NSdns1.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○NSdns1.registrar-servers.com,2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○NSdns2.name-services.com2017-03-14 → 2017-03-14 · 4 obs
○ 2016-07-05 05:44:14
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
○NSdns2.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○NSdns3.name-services.com2017-03-14 → 2017-03-14 · 4 obs
○ 2016-07-05 05:44:14
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
○NSdns3.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○NSdns4.name-services.com2017-03-14 → 2017-03-14 · 4 obs
○ 2016-07-05 05:44:14
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
○NSdns4.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○NSdns5.name-services.com2017-03-14 → 2017-03-14 · 4 obs
○ 2016-07-05 05:44:14
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
○NSdns5.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○NSjm1.dns.com2020-02-16 → 2020-02-16 · 4 obs
○ 2017-03-14 02:52:16
● 2020-02-16 17:17:12
○ 2026-04-13 21:32:46
○ 2026-06-16 23:33:36
● 2020-02-16 17:17:12
○ 2026-04-13 21:32:46
○ 2026-06-16 23:33:36
○NSjm2.dns.com2020-02-16 → 2020-02-16 · 4 obs
○ 2017-03-14 02:52:16
● 2020-02-16 17:17:12
○ 2026-04-13 21:32:46
○ 2026-06-16 23:33:36
● 2020-02-16 17:17:12
○ 2026-04-13 21:32:46
○ 2026-06-16 23:33:36
●NSns1.brandbucket.com2026-04-13 → 2026-06-16 · 3 obs
○ 2020-02-16 17:17:12
● 2026-04-13 21:32:46
● 2026-06-16 23:33:36
● 2026-04-13 21:32:46
● 2026-06-16 23:33:36
●NSns2.brandbucket.com2026-04-13 → 2026-06-16 · 3 obs
○ 2020-02-16 17:17:12
● 2026-04-13 21:32:46
● 2026-06-16 23:33:36
● 2026-04-13 21:32:46
● 2026-06-16 23:33:36
○MXeforward1.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○MXeforward2.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○MXeforward3.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○MXeforward4.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○MXeforward5.registrar-servers.com2016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
●A13.56.33.82026-04-13 → 2026-06-16 · 3 obs
○ 2020-02-16 17:17:12
● 2026-04-13 21:32:46
● 2026-06-16 23:33:36
● 2026-04-13 21:32:46
● 2026-06-16 23:33:36
○A154.84.112.352020-02-16 → 2020-02-16 · 4 obs
○ 2017-03-14 02:52:16
● 2020-02-16 17:17:12
○ 2026-04-13 21:32:46
○ 2026-06-16 23:33:36
● 2020-02-16 17:17:12
○ 2026-04-13 21:32:46
○ 2026-06-16 23:33:36
○A192.64.119.2282016-03-11 → 2016-07-05 · 4 obs
● 2016-03-11 08:30:18
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
● 2016-07-05 05:44:14
○ 2017-03-14 02:52:16
○ 2026-06-16 23:33:36
○A8.5.1.462017-03-14 → 2017-03-14 · 4 obs
○ 2016-07-05 05:44:14
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
● 2017-03-14 02:52:16
○ 2020-02-16 17:17:12
○ 2026-06-16 23:33:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net... | - |
| techtrojan.com | ns1.brandbucket.com, ns2.brandbucket.com | 2 records |
✅ Authoritative Response
Server:18.221.52.246
NS records: ns1.brandbucket.com, ns2.brandbucket.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for techtrojan.com (unsigned zone)
⏱️ Timing
Total: 189ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 13.56.33.8 |
| NS | 2 | ns1.brandbucket.com, ns2.brandbucket.com |
| TXT | 3 | 27aab5373841b85aab94982ee19ab62f96481ed6, afternic-verification-cvgUQU8SkLxsjXcPBS... |
| SOA | 1 | ns1.brandbucket.com mail.techtrojan.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)
Analysis
IP Addresses
techtrojan.com resolves to one IP address: 13.56.33.8.
eversponsor.com, rinkoro.com, duvena.com and two other host names share IP numbers with techtrojan.com.
Name Servers
The NS records for techtrojan.com delegate to ns1.brandbucket.com and ns2.brandbucket.com.
techtrojan.com uses the same name servers as several other domains — among them dropfat.com, trevexo.com, cavallion.com and two more.
The name servers for techtrojan.com overlap at least in part with those of other domains, including hopefunds.com and mistermessy.com.
These name servers commonly appear in combination with the name servers verification-koboazjhhcj7ojtkfkqd5g.ns101.verify.hn.
ns1.brandbucket.com resolves to 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361. Likewise, ns2.brandbucket.com resolves to 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8 — two IP addresses apiece.