Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Knowledge hub / DNS security

Knowledge hub

DNS security

Protecting the lookup system that turns your domain name into a server address.

Illustration explaining DNS security

What it means

DNS, the Domain Name System, is the lookup service that turns a name like example.com into the address of a server. DNS security is the set of controls that keep those answers correct, and that stop other people from changing your records.

DNS was designed in a more trusting age, and answers are not checked by default. If someone can alter a record, or trick a resolver into storing a false answer, your users can be sent to a server you do not control.

Why it matters

Whoever controls your DNS controls where your traffic goes, and where your email goes. A changed record can send customers to a fake login page, redirect mail to the attacker, or let someone obtain a valid TLS certificate for your domain. Few other failures are so complete.

It is often neglected because it works quietly. Old records for services you shut down can be claimed by others, which is subdomain takeover. An unlocked domain account with a weak password can lose you the name itself. Check the account protecting your domain as carefully as any production system.

How it shows up

The main controls are strong access to the registrar and DNS provider accounts with multi-factor authentication, a registrar lock, and regular review of records. DNSSEC adds digital signatures so resolvers can check that an answer is genuine, as described in RFC 4033. Encrypted lookups such as DNS over HTTPS protect users' queries from eavesdroppers.

Typical mistakes: dangling records that point at deleted cloud resources (see dangling DNS), too many people with edit rights, no alert when a record changes, and email records such as SPF and DMARC left incomplete. Keep an inventory of what each record is for.

Questions people ask

DNS security, answered

What is DNSSEC?

A set of extensions that adds digital signatures to DNS answers, so a resolver can check that the answer came from the domain's owner and was not altered on the way.

It protects the integrity of answers. It does not encrypt them, and it only works if both the domain and the resolver support it.

How can DNS be attacked?

By changing records through a stolen account, by poisoning a resolver's stored answers, by claiming dangling records, or by overwhelming a DNS provider with traffic.

Most real cases are account compromise or neglected records, not clever protocol tricks.

What is a registrar lock?

A setting at your domain registrar that blocks transfers and changes to the domain without extra steps. It helps stop a hijack that uses a stolen account or a fraudulent transfer request.

Ask your registrar which lock options they offer.

Does DNS security affect email?

Yes. Records for SPF, DKIM and DMARC live in DNS and decide whether others can send mail pretending to be you. An attacker who edits them can redirect your mail.

Review them with the same care as web records.

Who should have access to DNS?

As few people as possible, with multi-factor authentication, individual accounts and an audit trail. Treat the registrar login like a root credential.

Review who has access when staff or suppliers change.

Cyberlop mark

Do old records point at nothing?

Forgotten hostnames and exposed services are part of what an outside test looks at. We test your web app and its APIs and report what we actually reached, with proof. Ask us to run it on one of your applications.

Or start with a $199 pilot on one application: thirty days, success criteria agreed before day one, credited against the annual if you convert.