A hidden Unicode character, a subtle redirect, a certificate date, a subnet boundary, a header nobody checked.
Violet sees what your systems are hiding.
Bring me the thing that looks normal but is not. A character nobody can see. A query that grew teeth. A certificate about to expire. An address that refuses to behave.
VIOSCANS is a growing collection of practical technical tools with a little enchantment around the edges. Violet reveals hidden structure, explains why it matters, and points directly at what does not belong.
Pick a mystery. Violet has a tool for it.
Each tool is built around the sort of subtle problem that can consume an afternoon until somebody finally makes it visible.
Character Hunter
Find the invisible character that makes two values look identical while behaving completely differently.
Hunt characters βCensus of Symbols
Inventory every character, identify it, count it, and learn exactly what exists inside your text.
Count every symbol βViolet's SQL Loom
Turn compact, tangled SQL into something readable enough to review, explain, save, and trust.
Untangle SQL βVulnerability Scan
Inspect HTTPS behavior, headers, cookies, redirects, mixed-content clues, and visible security posture.
Scan a site βSSL Watch
Make certificate age, expiration, chain health, and trust signals visible before they become emergencies.
Inspect SSL βWebsite Watch
Observe responsiveness, DNS oddities, redirects, outages, and the behavior people actually experience.
See who's online βIP Playground
Turn CIDR, masks, ranges, broadcast addresses, private space, host counts, and reverse DNS into a picture.
Explore an address βViolet's Toolbox
Open the broader collection of practical utilities Violet keeps close when the problem gets strange.
Open the toolbox βThe odd little details are usually trying to tell you something.
VIOSCANS does not treat technical weirdness as background noise. It isolates the difference, gives it a name, and makes it understandable enough to act on.
Violet organizes the evidence so the technical problem stops feeling vague and starts becoming inspectable.
A result is useful only when you understand why it matters and what you can do next.
The strange thing gets pulled into the light, and the next move becomes much easier to see.
βSome problems hide in plain sight. Others require a census.β
Technical reality becomes easier when you can see the difference.
Three miniature examples show the idea behind some of Violet's most visual tools.
Looks the same. Is not the same.
account_numberaccΠΎunt_numberA single look-alike character can be enough to break equality, matching, imports, filters, and joins.
Find the hidden character βFrom command history to readable structure.
SELECT a, b, c
FROM table_a
JOIN table_b
ON ...
Send it through the loom β
A CIDR becomes a map.
Bring a mystery. Leave with something you can act on.
You bring Violet a mystery.
Text, SQL, a website, a certificate, an IP address, or behavior you cannot explain.
She inspects what others ignore.
The hidden character, subtle header, odd redirect, or boundary nobody visualized.
She highlights what does not belong.
The important difference gets moved out of the noise and into plain view.
She explains why it matters.
Because a result without context is just another technical number.
You fix it before it grows teeth.
Clarity turns investigation into action.
Technical tools can be serious without being cold.
Violet gives difficult technical work a recognizable guide, a little curiosity, and enough personality to make the investigation memorable without getting in the way of the answer.
Surface the thing that matters instead of flooding the screen with noise.
Violet is part of the explanation, not decoration pasted on top of it.
Built for developers, DBAs, sysadmins, network engineers, web teams, and curious people.
A clearer truth.
Even if the bug crawled out of a basement...
Violet will still go looking for it. Hidden files. Forgotten servers. Weird characters. Suspicious behavior. Some mysteries just require a little more dusting off.
Open Violet's toolbox
What strange little problem are we looking at next?
Start with the character that should not be there, the SQL nobody wants to read, or the system behavior that needs explaining.