threadsignal.com - dns.ninja
threadsignal.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 | v=spf1 -all | ||||||
| TXT | afternic-verification-cvgUQU8SkLxsjXcPBSk2CM | ||||||
| TXT | 27aab5373841b85aab94982ee19ab62f96481ed6 | ||||||
| SOA | ns1.brandbucket.commail@threadsignal.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=1785305927 | ||||||
Same first word
threadsignal.com |
Similar names
DNS History
3 records (3 active, 0 former)
●NSns1.brandbucket.com2026-03-19 → 2026-07-29 · 2 obs
● 2026-07-29 06:48:32
●NSns2.brandbucket.com2026-03-19 → 2026-07-29 · 2 obs
● 2026-07-29 06:48:32
●A13.56.33.82026-03-19 → 2026-07-29 · 2 obs
● 2026-07-29 06:48:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| threadsignal.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 threadsignal.com (unsigned zone)
⏱️ Timing
Total: 220ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 13.56.33.8 |
| NS | 2 | ns1.brandbucket.com, ns2.brandbucket.com |
| TXT | 3 | v=spf1 -all, afternic-verification-cvgUQU8SkLxsjXcPBS... |
| SOA | 1 | ns1.brandbucket.com mail.threadsignal.co |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)
Analysis
IP Addresses
threadsignal.com resolves to just one IP address, 13.56.33.8.
Two other host names, along with bankient.com, botanicalgirl.com and cipherking.com, also share IP numbers with threadsignal.com.
Name Servers
The NS records for threadsignal.com delegate to ns1.brandbucket.com and ns2.brandbucket.com.
threadsignal.com shares its NS records with other domains, for example vikinglord.com, infinityphase.com, bethalf.com and two others.
The name servers for threadsignal.com overlap at least in part with those of other domains, including spylytics.com and epicrift.com.
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.