How to Block Non-Encrypted Websites via Web Filter String Matching?

A company’s web filter is configured to scan the URL for strings and deny access when matches are found. Which of the following search strings should an analyst employ to prohibit access to non-encrypted websites?

encryption=off
http:// Source Reference Answer
www.*.com
:443

Community Votes

100%

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

Community Insight

It tests recognition of protocol prefixes for encryption status, with the common trap being confusion between URL string matching and network port analysis.

This SY0-701 question evaluates your ability to identify URL scheme indicators used in web filtering. The community consensus confirms that scanning for the 'http://' prefix is the most direct method to block unencrypted traffic while preserving secure connections.

Candidates frequently select option D (:443) because they associate port 443 with security; however, string-based web filters analyze the visible URL syntax rather than underlying TCP ports, making :443 irrelevant for blocking non-encrypted sites.

Community Discussion (8 comments)

SHADTECH123 👍 9 Selected: B

Blocking the string "http://" is the best way to prohibit access to non-encrypted websites. Non-encrypted websites use HTTP, while encrypted websites use HTTPS. This ensures only non-encrypted traffic is blocked without affecting encrypted websites. A. encryption=off: Not a consistent identifier for non-encrypted websites. C. www.*.com: Too broad, blocks both encrypted and non-encrypted websites. D. :443: Indicates HTTPS traffic, blocking it would deny access to encrypted websites.

dbrowndiver 👍 3 Selected: B

The http:// string in a URL indicates that the website is using the Hypertext Transfer Protocol (HTTP) without encryption. HTTP does not provide encryption, meaning data transmitted between the user and the website can be intercepted and read by third parties. Scenario Application: Identifying Non-Encrypted Sites: By scanning for the http:// string, the web filter can identify URLs that begin with this protocol, which signifies a lack of encryption. Blocking these URLs effectively prevents users from accessing non-encrypted websites. Security Enhancement: Prohibiting access to http:// ensures that users are only visiting websites that use HTTPS (https://), which encrypts data and provides a secure communication channel. Scanning for http:// directly targets non-encrypted web traffic, making it the most appropriate choice for denying access to such sites. This ensures that only encrypted websites, which protect data privacy and integrity, are accessible.

PAWarriors 👍 2 Selected: B

http:// --> Non encrypted websites. https:// --> Encrypted websites > Correct answer is B.

sahir47 👍 1

as it searches for a string match in a URL so the answer would be B as when the http:// is typed in the url a match will be found and the access would be blocked

MAKOhunter33333333 👍 2 Selected: B

A: idk, never seen this in a URL B: Specific to unsecured websites C: This can resolve to literally any site HTTP or HTTPS, to vague D: port 443 is https/secure

Jimmy1017 👍 1 Selected: B

Http is not secure but https is.

shady23 👍 1 Selected: B

http://

Mehsotopes 👍 2 Selected: B

http:// is an insecure protocol running on port 80 that uses unencrypted traceable data for communication on uncertified, & unprotected websites. It is indicated that you are on one of these insecure websites by a warning, or lack of padlock in your web search URL.

Comments & Corrections

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

Expert Analysis

Why the Answer Is Correct

Option B (http://) is the correct choice because web filters performing string matching operate at the application layer by inspecting the Uniform Resource Identifier (URI) scheme. The http:// prefix explicitly denotes traffic transmitted over plain Hypertext Transfer Protocol without Transport Layer Security (TLS). By configuring the filter to deny requests containing this exact string, administrators can effectively block all non-encrypted web access before any data leaves the client.

Why the Other Options Are Wrong

Option A (encryption=off) is incorrect because it is not a standardized URL parameter or protocol indicator used by modern browsers or servers. Option C (www.*.com) is excessively broad; using wildcards in string matching would inadvertently block both secure (https://www.example.com) and insecure domains, violating least-privilege principles. Option D (:443) represents the default TCP port for HTTPS traffic, but URL string filters do not parse network socket information, and matching this string would actually target encrypted sites rather than unencrypted ones.

Community Comment Notes

The community overwhelmingly validates option B, emphasizing the fundamental distinction between HTTP and HTTPS traffic. Comment [1] highlights that blocking http:// ensures only unencrypted traffic is restricted without impacting secure websites. Comment [2] reinforces this by explaining how identifying the protocol prefix allows precise filtering of traceable data. Comment [4] correctly notes that :443 is tied to secure communications, further confirming why option B remains the only logical choice for this scenario.

Official Reference

Exam Strategy

When answering web filtering questions, always differentiate between application-layer URL parsing and network-layer port inspection. Memorize that http:// signals unencrypted traffic in the browser address bar, making it the primary target for content control policies.

Related Analysis

Practice All SY0-701 Questions

Access 100 questions with complete answers and detailed explanations.

View Full SY0-701 Practice Test →

← Back to SY0-701 Study Guide