String Obfuscator
Obfuscate email addresses and phone numbers into HTML numeric entities to shield them from scrapers.
About String Obfuscator
Web developers, security researchers, and email marketing specialists frequently need to protect plaintext email addresses, contact telephone numbers, and sensitive strings from automated web scraping bots. Harvester bots crawl public HTML source code searching for mailto: links and raw text patterns to populate spam lists.
Masking text using standard HTML numeric character references, hex entities, or Unicode escapes makes strings unreadable to basic scraping scrapers while rendering legibly to human site visitors in modern web browsers.
This in-browser string obfuscator converts plaintext into multiple web-safe encoded formats including decimal HTML entities, hexadecimal entities, URL percent encoding, and JavaScript character code arrays.
To prepare sanitized demo copy, scramble character sequences using the word scrambler or convert strings with the binary code translator.
Step-by-step practical guide
- Type or paste the email address, phone number, or text string into the workbench input box.
- Select your desired obfuscation format: Decimal HTML Entities, Hex Entities, Mixed Random Entities, or JavaScript String.fromCharCode.
- Click Obfuscate String to generate the encoded string format immediately.
- Inspect the live rendered browser preview to confirm that the text renders normally to human eyes.
- Review the raw encoded code snippet ready for pasting into your HTML templates.
- Click Copy Obfuscated Code to transfer the snippet to your clipboard.
Engineering specifications and execution details
Encodes characters into standard decimal HTML numeric entities (&#nn;) using String.charCodeAt().
Encodes characters into hexadecimal entities (&#xNN;) using base-16 number conversions.
Generates randomized mixed-mode encoding to vary pattern signatures across successive characters.
Generates browser JavaScript execution strings (String.fromCharCode(...)) for dynamic DOM insertion.
Runs locally in browser JavaScript without transmitting confidential contact details over the network.
Data privacy and memory isolation
All email addresses, personal phone numbers, and sensitive strings remain strictly on your local device.
No personal data is collected, logged, or distributed across marketing aggregators.
Common production use cases
- Webmasters encoding contact email addresses on public web pages to reduce unsolicited bot spam.
- Frontend developers disguising phone numbers and contact details inside static site footers.
- Security researchers testing how web application firewalls and input sanitizers handle encoded payloads.
- Email template designers protecting footer contact links from aggressive email scrapers.
- Educational trainers demonstrating character set encodings and entity representation in computer science courses.
Edge cases and operational boundaries
- Sophisticated headless browsers: Headless crawlers executing full JavaScript and DOM rendering can still read rendered text; entity encoding stops standard regex scrapers.
- Screen readers: Modern screen readers decode standard HTML entities cleanly, allowing visually impaired users to hear content accurately.
- Long paragraphs: Obfuscating very long blocks of text expands HTML source size by 400 to 600 percent; use primarily for emails and short contact strings.
- Special symbols: Ampersands and quotes are properly converted to prevent HTML entity collisions.
Frequently Asked Questions
How does HTML entity obfuscation stop spam bots?
Spam bots scan HTML source code for patterns like name@domain.com. When encoded as decimal entities, the source code contains numbers and ampersands, which naive scrapers skip, while browsers still display the email to human visitors.
Will website visitors notice any difference in how text looks?
No. Web browsers automatically decode HTML entities when rendering pages, so the text appears completely normal to human visitors.
Does this prevent search engines from indexing the text?
Modern search engines like Google decode HTML entities, so important content may still be indexed while remaining shielded from basic scraping bots.
What is the difference between decimal and hex HTML entities?
Decimal entities use base-10 character numbers (@ for @), while hex entities use base-16 hexadecimal codes (@ for @). Both are standard HTML specifications.
Is entity obfuscation a replacement for CAPTCHA or user authentication?
No. Obfuscation is an anti-scraping barrier for public contact info. High-security data should always be protected with server-side authentication and CAPTCHA systems.
Are my email addresses sent to any third-party database?
No. All conversion algorithms execute locally in your web browser memory with zero network transmission.