Extract Email and URL Candidates From Text
Find address-like and HTTP(S) strings, remove exact duplicates, and review matching limits.
Email and URL extractors save time when a note contains many links or addresses. They scan the pasted text with patterns and return one unique match per line. The matches are candidates, not verified contacts or safe destinations. A quick review of boundaries and context is essential before using the result.
In this guide
Email matching rules
The Email Extractor looks for a familiar local-part, an @ sign, a domain with a dot, and a final alphabetic suffix of at least two letters. It accepts letters, digits, dots, underscores, percent signs, plus signs, and hyphens in the local part. It does not implement every valid email syntax and does not check whether a mailbox exists.
Matching is case-insensitive, but duplicate removal uses exact string equality after matching. Differently cased versions may both remain. The tool does not normalize domains or strip every possible bit of surrounding punctuation. Inspect a few results against the original passage.
InputContact ada@example.comOutput
ada@example.com
URL matching rules
The URL Extractor finds strings beginning with http:// or https:// and continues until whitespace, angle brackets, or a quote. This is a useful broad pattern for prose, but it may include a trailing comma, period, or closing parenthesis. The current implementation does not trim that punctuation automatically.
It does not extract bare domains such as example.com without a scheme, and it does not test whether the page is reachable. An extracted link is simply a substring that matches the pattern. Review it before opening or sharing.
InputSee https://example.com/page.Output
https://example.com/page.
Duplicates and context
Each tool removes exact duplicate strings while retaining the first occurrence order. That makes a concise checklist, but it also loses how many times an item appeared and where it appeared. Keep the source passage when surrounding context matters.
If a document contains private correspondence or sensitive records, handle it according to your own data rules. The code shown for these browser tools performs the extraction in the page, but that observation is not a guarantee about every browser extension, network environment, or future site version.
Use a short verification pass
Paste a representative paragraph with one ordinary match, one duplicate, and one address or URL next to punctuation. Compare each output line with the source. Remove a trailing sentence period from a URL when it is punctuation rather than part of the address. For more complex validation, use a format-aware parser or service appropriate to the task.
A useful edge-case test includes a URL followed by a period and an email address followed by a comma. The broad URL matcher may include the period, while the email pattern usually stops before the comma because comma is outside its allowed characters. This asymmetry is why reviewing the resulting list matters. If the result will drive outreach or automation, add independent validation and human review before acting on it.
- Look for punctuation at URL ends.
- Treat matches as candidates.
- Retain context for important decisions.
Frequently asked questions
Does the URL tool trim a final period?
No. A period is permitted by its broad pattern and can remain in the match.
Does an email match prove the inbox exists?
No. The pattern only recognizes address-like text.
Are matches case-normalized?
No. Matching ignores case, but the output preserves the source spelling and exact duplicate comparison.