Third-Party Risk ManagementNov 17, 20269 min read

What does an external security scan check? TLS, email, headers and exposed services

resources.items.externalScanChecks.heroAlt
CR

CyberRank Research

Part of: Free Security Rating

An external security scan checks the internet-facing parts of an organisation: which domains and subdomains it exposes, how they encrypt traffic, whether its email domain is protected against spoofing, which security headers its websites send, and whether any public service runs software with known vulnerabilities. It does this from outside, without credentials. Knowing exactly what each check tests helps you read results correctly and fix the right things. CyberRank runs these checks across a main domain and its subdomains and turns the findings into an AAA–D rating.

TL;DR

  • External scans start with asset discovery: you cannot assess a subdomain you have not found.
  • The core checks are TLS, email authentication (SPF, DKIM, DMARC), security headers and exposed services.
  • Each check maps to a public standard, such as RFC 8446 for TLS 1.3 or RFC 7489 for DMARC.
  • Findings are prioritised by severity; exposed software with known vulnerabilities usually comes first.
  • CyberRank scans the main domain and its subdomains, prioritises findings by severity and provides fix guides.

What is an external security scan?

An external security scan is an automated, unauthenticated assessment of an organisation's public-facing assets. Unlike an internal vulnerability scan, it has no network access or login, so it sees what an attacker on the internet would see.

It is the technical engine of an outside-in assessment, described in our explainer on outside-in security assessments.

The checks in an external security scan
Asset discoveryWhat it testsDomains, subdomains and servers linked to the organisationReference standardDNS; Certificate Transparency (RFC 6962)How CyberRank helpsAutomated discovery of public-facing assets
TLS and certificatesWhat it testsProtocol versions, cipher suites, certificate validityReference standardRFC 8446 (TLS 1.3); RFC 8996How CyberRank helpsChecks TLS/SSL configuration and certificates
Email authenticationWhat it testsSPF, DKIM and DMARC recordsReference standardRFC 7208, RFC 6376, RFC 7489How CyberRank helpsChecks email security records
Security headersWhat it testsHSTS, CSP and related browser protectionsReference standardRFC 6797 (HSTS); OWASP guidanceHow CyberRank helpsChecks security headers
Exposed servicesWhat it testsOpen services, admin pages, software versions with known CVEsReference standardCVE, CVSS v4.0, CISA KEVHow CyberRank helpsVulnerability scanning with severity prioritisation
Quantum-vulnerable key exchangeWhat it testsWhether public endpoints offer post-quantum key exchangeReference standardNIST FIPS 203How CyberRank helpsQuantum-crypto exposure signal (Beta)

One list instead of six

How CyberRank helps: CyberRank runs each of these checks as part of one assessment, so you get one prioritised list rather than six tool outputs.

How does asset discovery find subdomains?

Asset discovery builds the list of what to scan. Two public sources do most of the work: DNS records and Certificate Transparency logs.

DNS records reveal hostnames, mail servers and name servers. Certificate Transparency logs, defined in RFC 6962, publicly record TLS certificates as they are issued, so any subdomain that has had a certificate is usually discoverable.

This is why forgotten subdomains matter. A test environment from three years ago, with a certificate still on record, remains part of your attack surface until it is removed. Discovery can also over-reach: a subdomain pointing to a third-party service may belong to that provider, so good tools let you confirm or exclude assets.

How CyberRank helps: CyberRank's assessment covers the main domain and its subdomains, and auto-discovered vendors are added only after customer confirmation.

What does a TLS check test?

Transport Layer Security (TLS) protects data in transit between a browser or mail server and your systems. A TLS check connects to each public endpoint and records protocol versions, cipher suites, certificates and key exchange.

  • Protocol versions. RFC 8996 formally deprecated TLS 1.0 and 1.1 in March 2021. TLS 1.2 is the practical minimum, and TLS 1.3 (RFC 8446) should be supported.
  • Cipher suites. Weak or obsolete ciphers, such as those without forward secrecy, are flagged.
  • Certificates. Expiry dates, hostname mismatches, self-signed certificates and incomplete chains.
  • Key exchange. Whether the endpoint offers post-quantum or hybrid key exchange. NIST published FIPS 203 (ML-KEM) in August 2024 as the first standard post-quantum key-encapsulation mechanism.

Why the post-quantum check matters

The post-quantum check matters for data that must stay confidential for years, because of the risk explained in our article on harvest now, decrypt later. How CyberRank helps: CyberRank checks TLS configuration and certificates, and its quantum-crypto exposure signal (Beta) shows which endpoints still rely on quantum-vulnerable key exchange.

How is email authentication checked?

Email authentication is checked by looking up three DNS records for each sending domain: SPF, DKIM and DMARC.

  • SPF (RFC 7208) lists the servers allowed to send mail for the domain.
  • DKIM (RFC 6376) publishes a public key so receivers can verify a message's signature.
  • DMARC (RFC 7489) tells receivers what to do when SPF and DKIM fail, and where to send reports.

A typical starting DMARC record

A typical starting DMARC record looks like this:

_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

From monitoring to enforcement

p=none only monitors. Once reports show that legitimate mail passes, move to p=quarantine and then p=reject. A scan usually flags a missing record as a clear finding and p=none as a weaker one. Missing DMARC makes your domain easier to use in phishing against your customers.

How CyberRank helps: CyberRank checks SPF, DKIM and DMARC as part of every assessment.

Which security headers matter?

Security headers are instructions a website sends to the browser. They do not fix vulnerabilities, but they limit how easily some attacks succeed.

Common security headers
Strict-Transport-Security (HSTS)What it doesForces browsers to use HTTPS (RFC 6797)Common findingMissing, or a very short max-ageHow CyberRank helpsCovered by security header checks
Content-Security-PolicyWhat it doesRestricts where scripts and content can load fromCommon findingMissing, or allows unsafe inline scriptsHow CyberRank helpsCovered by security header checks
X-Content-Type-OptionsWhat it doesStops browsers guessing content typesCommon findingMissing nosniffHow CyberRank helpsCovered by security header checks
X-Frame-Options or frame-ancestorsWhat it doesPrevents the page loading in hidden framesCommon findingMissing, allowing clickjackingHow CyberRank helpsCovered by security header checks
Referrer-PolicyWhat it doesLimits what URL data is shared with other sitesCommon findingMissingHow CyberRank helpsCovered by security header checks

Keeping headers in proportion

The OWASP Secure Headers Project maintains current recommendations. How CyberRank helps: header findings sit in the same prioritised list as other findings, so they are weighed against more serious issues rather than inflated.

How are exposed services and known vulnerabilities identified?

The scanner checks which services answer on public addresses and what software they reveal through banners, headers or behaviour, then compares versions against public vulnerability records.

A CVE is an identifier for a known vulnerability; CVSS is a severity score, now in version 4.0, maintained by FIRST. CISA's Known Exploited Vulnerabilities catalogue shows which CVEs are being exploited in the wild.

Typical findings include exposed admin panels, database or remote-access services open to the internet, and web servers running unpatched software. Our article on PHP2Shell vendor exposure is a recent example of how a single runtime flaw affects many suppliers at once. Version detection has limits: some vendors backport fixes without changing version strings, so a finding can be a false positive.

How CyberRank helps: CyberRank prioritises findings by severity and provides fix guides; vendors can review findings and request re-evaluation if a fix is not visible.

How to act on external scan results

Confirm the asset list, fix exploitable findings first, then certificates, DMARC and headers, retire what you do not need, and re-scan.

The scan and re-scan in steps 1 and 7 below are automated; the fixes are your infrastructure and email teams' work. For a non-technical version of this process, see our guide on how to check your company's security posture from the outside. How CyberRank helps: CyberRank reassesses monitored organisations nightly, so fixes show in the next cycle.

  1. Confirm the asset list. Remove assets that are not yours and add any that were missed.
  2. Fix exploitable findings first. Exposed software with known, exploited vulnerabilities and exposed admin interfaces come before configuration findings.
  3. Fix certificates and TLS next. Renew expiring certificates, automate renewal and disable TLS 1.0 and 1.1.
  4. Publish and tighten DMARC. Start at p=none, review reports, then enforce.
  5. Add missing security headers. Apply them centrally, for example at a load balancer or CDN, so new sites inherit them.
  6. Retire what you do not need. Every unused subdomain removed is one less finding to defend.
  7. Re-scan and record. Confirm each fix is visible from outside and keep the result as evidence.

Where CyberRank does not help

CyberRank's external scan does not authenticate, exploit vulnerabilities or test application logic, so it cannot find flaws behind a login or inside your network. It does not detect cloud misconfigurations that are not publicly exposed, and it cannot confirm whether a backported patch is installed when the version string does not change. It also cannot apply fixes. For these gaps you need authenticated vulnerability scanning, penetration testing, cloud security posture tooling and your own change management.

Conclusion

An external security scan answers a narrow but important question: what does your public footprint reveal? It discovers assets, tests TLS and certificates, checks email authentication and security headers, and matches exposed software against known vulnerabilities. Each check rests on a public standard, so findings are explainable and fixable. Fix exploitable exposures first, then configuration, and re-scan to confirm. CyberRank brings these checks together in one prioritised assessment across your domain and subdomains.

References

  1. IETF, RFC 8446: TLS 1.3 (August 2018)
  2. IETF, RFC 8996: Deprecating TLS 1.0 and TLS 1.1 (March 2021)
  3. IETF, RFC 6962: Certificate Transparency (June 2013)
  4. IETF, RFC 7208: SPF (April 2014)
  5. IETF, RFC 6376: DKIM (September 2011)
  6. IETF, RFC 7489: DMARC (March 2015)
  7. IETF, RFC 6797: HTTP Strict Transport Security (November 2012)
  8. NIST, FIPS 203: Module-Lattice-Based Key-Encapsulation Mechanism Standard (August 2024)
  9. FIRST, Common Vulnerability Scoring System v4.0 (November 2023)
  10. CISA, Known Exploited Vulnerabilities Catalog (accessed 17 November 2026)
  11. OWASP, Secure Headers Project (accessed 17 November 2026)

Short answers that connect this article with our other guides.

Frequently asked questions

Run an external scan on your domain

The free Cybersecurity & Privacy Rating checks TLS, email authentication, security headers and exposed services from a URL.

Run an external scan on your domain