IPv4 Exhaustion and IPv6: Why the Internet Ran Out of Addresses
On 3 February 2011 the last blocks of IPv4 addresses were handed out. Learn why the internet ran short, what IPv6 changes, and what it means for you.
Read the articleGuides for running a site, setting up email and moving between hosts, plus updates from our team.
On 3 February 2011 the last blocks of IPv4 addresses were handed out. Learn why the internet ran short, what IPv6 changes, and what it means for you.
Read the articleLet's Encrypt launched in 2015-2016 and gave away SSL certificates. See how the web moved from plain HTTP to HTTPS, and why every site now needs a certificate.
CSS was proposed in 1994 by Håkon Wium Lie at CERN. Follow its path from CSS1 to Flexbox and Grid, and see why clean stylesheets matter for your site.
Brendan Eich built the first JavaScript at Netscape in May 1995. See how a quick prototype became ECMAScript, AJAX, Node.js and the language of the web.
In 2006 Amazon launched S3 and EC2 and began renting computing by the hour. Learn how AWS started cloud computing and how it relates to VPS and web hosting.
The iPhone arrived in 2007 with a real web browser in your pocket. See how smartphones, responsive design and mobile-first indexing changed how sites are built.
In 1965 Gordon Moore noticed chip components doubling regularly. See how Moore's law drove cheaper computing, hosting and the cloud, and where it slows.
In 1947 operators of the Harvard Mark II taped a real moth into their logbook. See the story of the first computer bug and how debugging became a discipline.
Unix began in 1969 at Bell Labs with Ken Thompson and Dennis Ritchie. Learn how its ideas and the C language shaped Linux, macOS and almost every server.
In 1998 Netscape released its browser code and a group coined the term open source. Read how this changed software and why it matters to website owners.
In 1983 Richard Stallman announced GNU, a free Unix-like system. See how the GPL and the four freedoms shaped the software behind your website.
In August 1991 a Finnish student announced a free operating system as a hobby. Read how Linus Torvalds's Linux kernel came to power servers, phones and hosting.
Wikipedia went live on 15 January 2001, built on wiki software and open licensing. Read how Jimmy Wales and Larry Sanger started it and how it runs today.
In 1998 two Stanford students built a search engine that ranked pages by their links. Read how Google and PageRank began and what it means for your website.
Between 1995 and 2000 internet stocks soared, then collapsed. Read what caused the dot-com bubble, who survived, and the lessons it left for online businesses.
WordPress started in 2003 as a fork of an abandoned blogging tool. Learn how Matt Mullenweg and Mike Little built it and why it became so widely used.
MySQL was created in Sweden and released in 1995, then bought by Sun and Oracle and forked as MariaDB. Here is how the web's favourite database evolved.
PHP began in 1994 as a set of scripts for Rasmus Lerdorf's own home page. This is how it grew into the language that powers WordPress and much of the web.
LAMP is the combination of Linux, Apache, MySQL and PHP that ran much of the early web. Learn where the term came from and why it still matters for hosting.
Web hosting began with servers under desks and grew into shared hosting, VPS, dedicated servers and the cloud. See how each stage solved a real problem.
In 1995 a group of webmasters began patching NCSA's web server. Apache became the world's most used web server. Read the history of its rise and what followed.
From Netscape versus Microsoft in the 1990s to Chrome's rise after 2008, the browser wars shaped web standards. Learn what happened and why it still matters.
NCSA Mosaic put images in web pages in 1993, and Netscape Navigator turned the web into a mass medium. Here is how two browsers changed the internet.
The first website went live at CERN on a NeXT computer in 1990-91. See what the original page said, how it worked, and how CERN restored it decades later.
In 1989 a physicist at CERN proposed a system of linked documents. Learn how Tim Berners-Lee created HTTP, HTML and the first browser, and gave the web away.
On 15 March 1985 a Massachusetts computer company registered symbolics.com, the first .com domain name. Here is the story of that name and what came after.
Before DNS, one file called HOSTS.TXT listed every computer on the network. See how Paul Mockapetris created the system behind every web address in 1983.
In 1971 engineer Ray Tomlinson sent a message between two computers and chose the @ symbol for addresses. The history of email, from ARPANET to your inbox.
On 1 January 1983 ARPANET switched every host from NCP to TCP/IP in one coordinated move. Here is the story of the protocols behind the modern internet.
On 29 October 1969 a computer at UCLA tried to send the word LOGIN to Stanford Research Institute. Here is how ARPANET began and why its design still matters.
In March 2024 a developer noticed a slow SSH login and uncovered a backdoor planted in xz Utils over two years. See the story and what it means for open source.
In 2023 the Cl0p group exploited a SQL injection flaw in MOVEit Transfer and stole data from over 2,000 organisations. See what happened and how to respond.
Log4Shell, found in Log4j in December 2021, let attackers run code on servers with a single text string. See why it spread and how to track dependencies.
In July 2021 REvil abused Kaseya's remote management tool to hit service providers and their customers. See how it spread and what it means for agencies.
In May 2021 ransomware shut down Colonial Pipeline and caused fuel shortages across the US East Coast. See how one unused account helped, and why 2FA matters.
In 2020 attackers hid malware in a routine SolarWinds Orion update sent to thousands of organisations. See how it worked and why plugin hygiene matters.
In July 2020 attackers hijacked famous Twitter accounts by tricking staff by phone. See how social engineering reached internal tools and what to learn.
A misconfigured firewall let a former cloud engineer reach data on 100 million Capital One customers in 2019. See how SSRF and over-broad permissions combined.
Marriott disclosed in 2018 that its Starwood guest database had been breached since 2014. Learn what was taken and why due diligence and logging matter.
In January 2018 researchers revealed Meltdown and Spectre, flaws in how modern CPUs work. See what they allow and why they matter for hosting and isolation.
Equifax lost data on about 147 million people in 2017 after missing a patch for Apache Struts. See the timeline, the expired certificate and the lessons.
NotPetya began with a poisoned accounting update in Ukraine and shut down firms worldwide in 2017. See how it spread and what Maersk's recovery teaches.
WannaCry spread to over 150 countries in May 2017 using a Windows flaw that had been patched two months earlier. See what happened and why updates matter.
Yahoo disclosed huge breaches in 2016 and later said all 3 billion accounts were affected in 2013. A look at what happened, the price cut and what it teaches.
In October 2016 a botnet of hacked cameras and routers disrupted Twitter, Netflix and more by attacking DNS provider Dyn. See how it worked and why it matters.
Hackers tried to steal nearly 1 billion dollars from Bangladesh Bank in 2016 via SWIFT. A spelling error stopped much of it. Here is what it teaches.
In December 2015 hackers cut power to about 225,000 people in Ukraine. See how the attack worked and which remote access lessons apply to every website.
The Impact Team's 2015 leak of Ashley Madison data exposed millions of users and a broken 'full delete' promise. A case study in data retention and passwords.
In November 2014 Sony Pictures was crippled by destructive malware and mass leaks. Here is what happened, who was blamed, and the backup lessons it left behind.
In 2013 attackers stole 40 million card numbers from Target after entering through a supplier's login. See how it happened and how to limit third-party risk.
Shellshock, disclosed in September 2014, let attackers run commands on servers through a flaw in Bash. See what it was and the lessons it taught server owners.
Heartbleed, disclosed in April 2014, let attackers read memory from servers running OpenSSL. See what it exposed and the steps every site owner should remember.
A Dutch certificate authority was hacked in 2011 and fake certificates were issued for Google and others. See how it unfolded and what it means for SSL today.
LulzSec hacked well-known sites for 50 days in 2011, often using basic SQL injection. Here is what happened and how site owners can avoid the same mistakes.
In April 2011 Sony took the PlayStation Network offline after a breach affecting about 77 million accounts. See what went wrong and what site owners can learn.
In 2011 security firm RSA disclosed an attack tied to its SecurID tokens, started by one phishing email. Here is what site owners should learn from it.
Stuxnet was a worm built to damage industrial equipment, found in 2010. Learn how it spread, why air gaps failed and what its story means for everyday security.
In January 2010 Google revealed a sophisticated attack from China. Operation Aurora showed how a browser flaw and a phishing link can open a whole company.
Conficker spread through an unpatched Windows flaw and weak passwords, building a botnet of millions. Here is how it worked and why patching still matters.
In 2007 retailer TJX disclosed one of the largest card thefts of its time. Here is how the thieves got in, and what website owners should take from it today.
Passwords began in the 1960s on a shared MIT computer. See how storage, hashing and salting evolved, and why the old rules about symbols and resets were wrong.
From Netscape's SSL 2.0 in 1995 through SSL 3.0 and TLS to the free certificates of today, here is how encrypted browsing became the default on the web.
From a 1978 ARPANET message to the Usenet Green Card spam of 1994 and the CAN-SPAM Act of 2003, here is how junk email grew and why the laws struggled.
MyDoom spread by email in January 2004 faster than any worm before it, opened backdoors and flooded SCO's website. Its author was never publicly identified.
In April 2004 Sasser crashed computers worldwide with no user action. An 18-year-old German who wrote it at 17 was caught after a bounty tip. The story of a self-spreading worm.
In August 2003 Blaster used a Windows RPC flaw to crash and restart PCs worldwide, with a message aimed at Microsoft. How it spread, and who was caught.
On 25 January 2003 a tiny worm infected most vulnerable SQL Servers in ten minutes and slowed the internet. What it teaches about patches and exposed databases.
One week after 11 September 2001, Nimda spread by email, web servers, shared drives and infected web pages. It showed why one patched hole is never enough.
In July 2001 Code Red infected hundreds of thousands of Windows web servers within hours and was aimed at whitehouse.gov. The patch had been out for a month.
In February 2000 a 15-year-old from Montreal knocked Yahoo, eBay, CNN and Amazon offline. This is how the first big DDoS wave worked, and how he was caught.
Two-digit years threatened computers in 1999. The millennium passed quietly, but only after years of costly repair work. What happened and what it taught.
On 4 May 2000 an email titled ILOVEYOU spread from the Philippines to parliaments and newsrooms. How the worm worked, and the law it forced the country to pass.
On 26 March 1999 a Word document emailed itself to 50 contacts at a time and overloaded mail servers. See how Melissa spread and how its author was caught fast.
In 1991 Phil Zimmermann released PGP while strong encryption counted as a munition. Follow the Customs probe, the Clipper chip and the fight over strong crypto.
How Diffie, Hellman and Merkle solved the key distribution problem in 1976, how RSA followed in 1977, and why the same maths protects every HTTPS site today.
From packet filters at DEC and Bell Labs to the first commercial firewalls and stateful inspection, here is how the firewall became the first line of defence.
After the Brain, Vienna and Jerusalem viruses, programmers in several countries wrote the first antivirus tools in 1987. Here is how signature scanning began.
The story of two famous hacker groups of the 1980s and 90s, the myths around their so-called war, and the 1992 indictments that ended Masters of Deception.
In May 1990 the US Secret Service raided hackers in 14 cities. The crackdown went wrong in important ways, and led to the Electronic Frontier Foundation.
In 1984 German hackers made a bank owe them 135,000 marks through a videotex flaw, then gave it back publicly. The story of Europe's famous hacker club.
On 6 March 1992 a boot sector virus was predicted to wreck millions of PCs. It did far less damage than feared, but taught lessons about backups and hype.
Kevin Mitnick's rise, his 1995 arrest and his later career show that people are often the weakest link, and why social engineering still works on small sites.
In 1986 astronomer Clifford Stoll followed a 75-cent accounting gap to a German hacker selling secrets abroad. A classic story of patient incident response.
In November 1988 a Cornell student's experiment brought thousands of machines to a crawl. The Morris worm led to a landmark CFAA conviction and the first CERT.
How a 1983 film, a gang of Milwaukee teenagers and a worried Congress led to the 1986 Computer Fraud and Abuse Act, which still defines hacking in US law.
Two brothers in Pakistan wrote a boot sector virus to protect their software and left their names inside it. This is the story of Brain, the first IBM PC virus.
In 1971 a program called Creeper crawled across the ARPANET saying 'catch me if you can', and Reaper was built to chase it. The story of the first network code.
The word hacker began as praise at MIT in the 1950s and 60s. Follow its path from model trains and campus pranks to headlines about break-ins and crime.
The story of John Draper, the toy whistle that made a perfect 2600 Hz tone, and what early phreaks taught Apple's founders about systems and hidden assumptions.
How a single 2600 Hz tone let curious teenagers control the Bell phone network, and why mixing data and commands is a mistake website owners can still avoid.