Terminator Sec
Endpoint and DNS control
Block, sinkhole, or prompt before a connection opens.
- Intercept
- Score
- Block
- Ask
- Allow
Security software organization
Two controls. The decision stays on systems you operate.
Endpoint and DNS control
Block, sinkhole, or prompt before a connection opens.
Cryptographic transition
Inventory public-key use, then move to ML-KEM and ML-DSA.
UDP, TCP, and DoH on the host.
Blocklist, then entropy, then wording.
Block, ask, or allow. Nothing leaves the device.
$ terminator-sec scan :5353
[+] trie loaded
[+] scoring udp/tcp/doh
12 names observed · 3 blocked · 1 prompt
Compiled in Go. Zero heap allocations per lookup cycle. Operates as a local DNS proxy (UDP/TCP/DoH :53) with zero external telemetry.
O(k) domain prefix & suffix matching across 500k+ IOC feeds.
Real-time DGA anomaly scoring without off-device cloud lookups.
Process-level attribution linking outbound queries to caller PIDs.
Pick a name. The host blocks, asks, or allows.
This name is already on a local blocklist.
Decision
Score the name to see what the host would do.
Known malware is blocked. Machine-generated names are blocked. Lookalike login pages ask the person first. Ordinary sites are allowed through.
CBOM of RSA, elliptic curves, and SHA-1.
Hybrid ML-KEM at the TLS edge.
ECDSA and ML-DSA on one certificate.
LMS only where a stateful signature fits.
Recorded ciphertext is the reason to plan now.
Research machines do not retire production RSA.
Legacy clients stay. PQC clients require ML-KEM.
Build a sample inventory. Each row is one component.
What you will see
Public-key systems that need a migration plan, and one edge that is already hybrid.
RSA and elliptic curves are the Shor concern. AES is a key-size note, not the same problem. Research machines do not retire production RSA this year.
| Where | Algorithm | Used for | What to do | Why |
|---|---|---|---|---|
| Build the inventory to walk the sample estate one component at a time. | ||||
Illustrative counts. Not a live tenant.
Sample data, in the browser. Nothing on your network is scanned.
Ask a question. The answer is a path through the nodes.
Retrieved path
Click a node, or ask a question.
Score a name or build the inventory first if you want those facts in the graph. RSA and elliptic curves are already here. AES is here as a different kind of note.
Endpoint rollout or cryptographic migration. We reply within four business hours.