Protect links and connections with safe habits
Combine careful communication checks, destination checks and encrypted connections to reduce online risk.
Exam scope and assessment notes
This sequence follows Cambridge IGCSE Computer Science 0984, 2026–2028 syllabus Version 4. It covers subject content sections 5.1–5.3 only. The separately published 2029–2031 syllabus is not mapped here. Practice is original, self-checked and does not award an official Cambridge grade. Full timed papers and human subject-teacher review remain outstanding. Cambridge states that 0984 has the same 2026–2028 subject content as 0478, with 9–1 grading. In June and November, Cambridge lists 0984 in Administrative zone 3 and for centres in Oman and the UAE. Confirm availability for your centre and exam series with Cambridge International. The separately published 2029–2031 syllabus changes to Python 3 only and removes pseudocode; this 2026–2028 route does not cover those changes.
Before you begin
- No programming language is required. Be comfortable with place value and multiplication; each lesson introduces the computer-science notation it uses.
Work on paper. Try each question before revealing help, and explain why your method works.
Quick readiness check
Why inspect a link's URL?
What you will learn
- Check spelling, tone and unexpected requests
- Inspect the destination URL
- Explain SSL wording and secure connection limits
People and connection checks complement technical tools
Unexpected urgency, spelling or tone changes can signal a deceptive communication. Check the sender and verify requests through a known channel instead of following a message's instructions automatically.
Apply and check the rule
Inspect the URL, especially the domain, before entering private information. The syllabus names Secure Socket Layer (SSL) as a security protocol; current secure web services use its successor TLS. An encrypted connection helps protect data in transit but does not prove the page is genuine, so combine it with URL and message checks.
Pause and explain
A page has a secure connection but the domain misspells the school's name. What should the user do?
Worked example
A message from a supposed school administrator asks for a password at a shortened link. Give two checks before acting.
Show the worked solution
- Check whether the request and tone are unexpected or urgent.
- Inspect the true destination domain rather than trusting the displayed text.
- Verify the request through a known school channel.
Answer Do not follow the shortened link. Check the actual destination and confirm the request with the school through a known contact method.
Try a topic test
Choose Easy, Normal or Difficult. Save your answers and open worked review after finishing.
Test this topic →From guided practice to a new situation
Write your answer and reasoning first. Use a hint only if you are stuck. The model solution is for self-checking; your written work is not automatically marked.
Name two clues in a message that could indicate phishing and one safe response.
Give me a hint
Look for pressure and an unexpected request.
Compare my reasoning
- Urgency, unusual tone or a suspicious link can be warning signs.
- Check the sender and actual destination.
- Verify the request through a known channel before sharing information.
Urgency and a suspicious link are warning signs; verify through a trusted channel rather than using the message link.
Look for these in your work
- Two clues
- Safe response
Explain what SSL/modern HTTPS can protect and why the user must still check the domain.
Give me a hint
Separate data-in-transit protection from site identity claims.
Compare my reasoning
- A secure protocol encrypts data while it travels.
- It helps establish a protected connection to a host.
- A malicious host can still serve deceptive content, so inspect the domain.
SSL is the syllabus term for a secure-connection protocol (modern web use is TLS). It protects data in transit, but the user still needs to verify the domain and purpose of the site.
Look for these in your work
- Connection protection
- Terminology
- Domain check
A message says an account will be deleted in five minutes and links to a page with HTTPS. Describe a safe sequence for handling it.
Give me a hint
Treat urgency and encryption as different evidence.
Compare my reasoning
- Pause instead of obeying the urgent instruction.
- Check the sender, spelling, tone and actual domain.
- Open the service through a bookmark or known address and contact support through a trusted route.
Do not use the message link. Verify the sender and domain, then visit the service through a known route and confirm the claim directly. HTTPS alone does not establish that the urgent message is legitimate.
Look for these in your work
- Pressure resisted
- Link checked
- Trusted verification
Common mistakes
- Trusting the visible link text without inspecting its destination
- Treating SSL or HTTPS as proof that a business claim is true
What can you explain now?
What does an encrypted connection fail to prove?
Compare with the explanation
That the website is genuine or honest
Encryption protects the connection, not the truth of the site's claims.
After trying it yourself, choose your next review. This is your self-assessment.
Your review choice appears on Today. Sign in to sync it across devices.
Make it stick
Name three user actions that help reduce phishing or connection risks.
If you needed the solution, close it and solve the problem again from a blank page. A correct answer is stronger when you can explain the reason for each step.