Why a Percent-Encoded String Renders as an Email Hyperlink

CS0-003 By islever Editorial Last updated

Short answer

B Percent-encoding like %77%77%77%2e obfuscates the real URL so the encoded text can slip past spam filters.

Question

A user reports a message as suspicious to the IT security team. An analyst reviews the message and notices that the following text string becomes a hyperlink in an email:
%77%77%77%2e%63%6f%6d%70%74%69%61%2e%63%6f%6d
Which of the following would most likely explain this behavior?
  1. The string contains obfuscated JavaScript shellcode.
  2. The text is encoded and designed to bypass spam filters. Correct Answer
  3. The email client has a parsing error elsewhere in the message.
  4. The sandboxed PC used for testing has non-default configurations.

Key Takeaways

The question tests recognition of percent-encoded URLs as an obfuscation indicator; the trap is mistaking the encoding for executable JavaScript shellcode or blaming the email client.

This CS0-003 question tests URL percent-encoding as a phishing technique: %77%77%77%2e%63%6f%6d%70%74%69%61%2e%63%6f%6d decodes to www.comptia.com, and the encoded form is used to bypass spam filters. The correct answer is B.

Common mistake: Option A: percent-encoding is only a character representation, not executable JavaScript or shellcode, so it cannot explain the hyperlink by itself.

Expert Analysis

The governing principle: percent-encoding in a URL. The string is standard URL percent-encoding, where each %XX pair is the hexadecimal ASCII code of one character. Decoding it — %77 = w, %77 = w, %77 = w, %2e = ., %63 = c, %6f = o, %6d = m, %70 = p, %74 = t, %69 = i, %61 = a, %2e = ., %63 = c, %6f = o, %6d = m — yields www.comptia.com. The email client renders this as a hyperlink because the decoded value is a well-formed URL, which is exactly the behavior a legitimate mailto/anchor link follows.

Why option B is correct. Attackers routinely percent-encode or otherwise obfuscate URLs so that signature- and reputation-based spam filters see an unrecognized, non-matching string instead of the actual destination domain. The security principle tested here is that obfuscated URL encoding is a common phishing indicator: the visible or raw text does not reveal the true landing site to either the recipient or the filter. Option B — the text is encoded and designed to bypass spam filters — matches that documented practice.

Why the other options fail. Option A is wrong because percent-encoding is a data representation, not executable code; nothing here is JavaScript, script tags, or shellcode, and the string alone does not run in the browser. Option C is wrong because the hyperlink is explained entirely by the encoded string itself; there is no need to invoke an unrelated parsing error. Option D is wrong because a sandboxed PC's non-default configuration does not cause a plain text string to become a hyperlink — the decoding happens in the mail client regardless of sandbox settings. The community comment also selects B (while mislabeling the explanation text), consistent with this analysis.

Bottom line: option B is the best explanation.

Exam Strategy

When a question shows a string of %XX pairs, decode a few bytes mentally (e.g., %77 = w, %2e = ., %6d = m) to reveal the pattern before reading the options; recognizing the decoded value usually settles the question immediately. Then eliminate options that describe mechanisms unrelated to what the string actually is — encoded data is not executable code, and client rendering is normal behavior, not a bug.

Frequently Asked Questions

What does the string %77%77%77%2e%63%6f%6d%70%74%69%61%2e%63%6f%6d decode to?

Each %XX pair is the hexadecimal ASCII code of a character: %77 = w, %2e = ., %63 = c, %6f = o, %6d = m, %70 = p, %74 = t, %69 = i, %61 = a. Decoded, the string is www.comptia.com, which is why the mail client renders it as a hyperlink.

How do attackers use URL encoding to evade spam filters?

They percent-encode or otherwise obfuscate links so signature- and reputation-based filters cannot match the raw string to known malicious domains. Analysts decode or sandbox-scan such links to reveal the true destination before taking action.

Is percent-encoded text the same as JavaScript shellcode?

No. Percent-encoding is a data representation scheme for URLs and text, not executable code. JavaScript would require script constructs, and shellcode requires machine instructions; neither is present in this string, which eliminates option A.

More CS0-003 FAQ →

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

  1. Joy329 👍 1 Answered B
    B. The string contains obfuscated JavaScript shellcode. The text is encoded and designed to bypass spam filters.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

← Back to CS0-003 Study Guide