Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is ThreatPort?
ThreatPort is an external attack surface management (EASM) and cyber threat intelligence platform. It scans the parts of your organization that are visible from the public internet — domains, subdomains, open ports, certificates, DNS and email records — and flags weaknesses that attackers could find first. It is agentless and self-serve: you point it at a domain and get findings without installing anything or sitting through a sales process.
What it actually checks
Based on the site's own description, a scan surfaces:
- Subdomains and exposed services you may not have inventoried
- Open ports and weak HTTP security headers
- Missing SPF or DMARC records, which affect email spoofing risk
- SSL/TLS certificate problems
- Technologies in use that map to known CVEs
- AI-assisted pentest-style reporting, with PDF-ready output
Who it fits
The stated audience is IT managers, CISOs, CTOs and small security teams. That is a meaningful distinction: this is not a full vulnerability management suite running inside your network. It answers the outside-in question — "what can someone on the internet see and try?" — which is exactly the gap lean teams tend to have.
A practical scenario: a 40-person SaaS company has a marketing site, an app subdomain, a staging environment someone spun up last year, and a support portal on a third-party host. Nobody owns the full list. An external scan produces that list plus the misconfigurations on it, which is also the evidence you need for auditor questions and customer security questionnaires.
Trade-offs to weigh
| Strength | Limitation to consider |
|---|---|
| Agentless, fast to start, free initial domain scan | External view only; nothing inside your network or on endpoints |
| Continuous monitoring on the paid tier | Per-domain pricing means cost scales with your domain count |
| Reporting aimed at leadership and compliance prep | Findings still need triage and remediation by your team |
The free scan is the sensible first step: run it against your primary domain and check whether the results match what you believed was exposed. If the subdomain list contains surprises, that is your answer on whether continuous monitoring is worth paying for. If you need internal asset discovery or endpoint detection, look at Tenable or Qualys instead — those solve a different problem.
How do I run a free domain scan to see what is exposed on my domain?
Go to ThreatPort and start a free domain scan by entering the domain you want checked, then review the results dashboard. The page presents this as a self-serve, agentless workflow: no installation or sales call is required to begin. The free scan is designed to surface subdomains, exposed services, open ports, weak HTTP headers, missing SPF or DMARC records, certificate issues, and technologies that may map to known vulnerabilities.
What the free scan typically shows
- Subdomains and exposed services — extra hostnames and internet-facing services you may not have inventoried.
- Open ports — services reachable from the public internet, which is often where unnecessary exposure starts.
- DNS and email security — missing or weak SPF and DMARC records that affect spoofing risk and deliverability.
- SSL/TLS issues — certificate problems or weak configurations on public endpoints.
- CVE mapping — detected technologies linked to known vulnerabilities, useful for prioritization.
- Header and configuration weaknesses — missing security headers and similar low-effort hardening gaps.
How to read the results
Treat the first scan as a baseline, not a verdict. Confirm ownership of every subdomain and service before acting, then sort findings by internet reachability and exploitability rather than raw count. A public login portal with an outdated component deserves faster attention than an informational page with a missing header.
The paid plan is listed at 50 USD per month per domain and adds continuous monitoring, deeper external attack surface analysis, AI-assisted pentest output, and PDF-ready reporting for remediation tracking, leadership updates, and compliance preparation. If you only need a one-time picture, the free scan is enough to start; if you need recurring evidence and reports, the paid tier is the relevant comparison.
A useful next step: run the scan, export or note the findings, and assign each item an owner and a due date. Re-scan after fixes to confirm the exposure is actually closed, since external changes can lag behind internal configuration updates.
What does the $50 per month per domain plan include compared to the free scan?
The $50 per month per domain plan turns a one-time discovery scan into continuous monitoring with reporting and AI-assisted analysis. According to the site, the free scan is a starting point: you point it at a domain and see what is publicly exposed — subdomains, exposed services, weak headers, missing SPF or DMARC records, certificate issues, and technologies that may link to known vulnerabilities. The paid plan adds ongoing external attack surface analysis, CVE mapping, DNS and email security checks, SSL monitoring, open port visibility, AI pentest output, and PDF-ready reporting.
Free scan vs. paid plan
| Capability | Free domain scan | $50/month per domain |
|---|---|---|
| Subdomain and exposed service discovery | Yes, as a starting scan | Yes, continuously monitored |
| Weak headers, SPF/DMARC, certificate issues | Surfaced in the scan | Checked as part of ongoing monitoring |
| CVE mapping | Not specified for the free tier | Included |
| Open port visibility | Not specified for the free tier | Included |
| AI-assisted pentest output | No | Included |
| PDF-ready reporting | No | Included |
| Continuous monitoring | No | Included |
Both are agentless and self-serve — no installation, and no enterprise sales call required.
Who gets the most from the upgrade
The paid tier fits a lean IT or security team that needs recurring evidence rather than a single snapshot. A practical example: you run the free scan on your primary domain, find a forgotten subdomain with an outdated service and a missing DMARC record, and fix both. The value of the $50 plan is catching the next one — a certificate about to expire, a new port opened by a developer, or a newly published CVE affecting a technology you already run — without remembering to rescan manually.
How to decide
- If you only need a one-off baseline before a project or audit, start with the free scan.
- If you must show remediation progress to leadership or prepare for compliance, the PDF reporting is the deciding feature.
- If your public footprint changes often — new subdomains, cloud services, marketing sites — continuous monitoring is the reason to pay.
- If you already run an internal vulnerability scanner, note that this covers the external view only; the two are complementary, not substitutes.
A sensible next step: run the free scan on one domain, note how many findings you would need to track over time, then judge whether per-domain pricing matches the number of domains you actually expose.
Can ThreatPort help me prepare evidence for compliance audits or leadership security reports?
Yes. ThreatPort is built around producing practical security evidence rather than just raw scan output: it maps external exposure to CVEs, checks DNS and email security records such as SPF and DMARC, monitors SSL certificates, and generates PDF-ready reporting intended for remediation tracking, leadership updates, and compliance preparation. For a lean team, that means the same scan can serve two audiences — a technical fix list for engineers and a summarized risk view for a CISO or auditor.
What evidence it can realistically support
- External attack surface inventory: subdomains, exposed services, and open ports give you a defensible picture of what is publicly reachable.
- Vulnerability mapping: linking discovered technologies to known CVEs supports vulnerability-management narratives.
- Email and DNS hygiene: missing or weak SPF and DMARC records are common audit findings, and these are directly checkable.
- Certificate and header issues: expired or misconfigured SSL and weak security headers are easy to evidence and easy to remediate.
- Reporting output: AI-assisted pentest reporting and PDF export reduce the manual work of turning findings into a document.
Where it fits and where it doesn't
ThreatPort is agentless and self-serve, so it suits organizations that need external-view evidence without a lengthy procurement cycle. A free domain scan is enough to test whether the output matches the format your auditor or board expects.
Be clear about scope, though. External attack surface management covers what is visible from the internet. It does not replace internal vulnerability scanning, endpoint controls, access reviews, or policy documentation that many frameworks also require. Treat it as one evidence stream, not the whole compliance file.
A practical next step
Run a free scan on one in-scope domain, then ask: does the report state findings in a way an auditor would accept — asset, issue, severity, evidence, remediation? If yes, the paid tier's continuous monitoring and PDF reporting become the natural next step for recurring leadership updates. If your audit is driven mainly by internal controls, pair it with an internal scanning or GRC tool instead.
How does ThreatPort monitor my attack surface continuously and alert me to new risks?
ThreatPort monitors your external attack surface by repeatedly scanning the public-facing assets tied to a domain and comparing each new result against what it saw before. Its page describes this as continuous external attack surface monitoring, with a free domain scan as the entry point and a paid plan that adds ongoing monitoring. The practical loop is: discover assets, fingerprint what is exposed, map findings to known risks, then notify you when something changes.
What gets watched
From the site's description, the monitored surface includes:
- Subdomains and exposed services — new hosts appearing under your domain are a common source of forgotten or shadow assets.
- Open ports — a service that becomes reachable from the internet is a change worth knowing about immediately.
- CVEs — detected technologies are linked to known vulnerabilities, so a version change can create a new finding.
- SSL/TLS certificates — expiry, misconfiguration and trust issues are tracked as part of the surface.
- DNS and email security — missing SPF or DMARC records and weak headers are surfaced as risks, since they affect spoofing and deliverability.
- Web server headers — weak or missing security headers are flagged.
How alerts reach you
The page presents ThreatPort as self-serve and agentless, meaning there is nothing to install on your hosts; discovery happens from the outside, the way an attacker would see you. Alerts are generated when a scan detects a new or changed exposure, and the paid tier adds AI-assisted pentest output plus PDF-ready reporting so a finding can be turned into a remediation ticket or a leadership update. The site also mentions an AI assistant that answers security questions and a dashboard framed as a command center for digital risk.
A concrete scenario
Suppose you run a small SaaS company. On Monday a developer spins up a staging subdomain with an admin panel on a non-standard port and a self-signed certificate. A continuous external scan picks up the new host, the open port, the certificate problem and any technology version with a matching CVE, and raises it as a new risk. Without continuous monitoring, that asset typically surfaces months later during a customer security review or an actual incident.
Choosing between free and paid
The free domain scan is best for a one-time inventory: what do I have exposed right now? The paid plan, described at 50 USD per month per domain, is for teams that need change detection over time, deeper analysis, AI pentest output and exportable reports. If your environment changes weekly — new deploys, new subdomains, rotating certificates — the continuous tier is the one that matches your risk. If you only need a periodic snapshot before an audit, the free scan covers the baseline.
Practical next step
Run the free scan on your primary domain, then compare the asset list against your own inventory. Any host, port or subdomain you cannot account for is the strongest argument for turning on continuous monitoring, because those are exactly the assets that change without anyone telling you.
What DNS, email security, SSL, and open port issues can ThreatPort detect for my organization?
ThreatPort is built to surface the externally visible weaknesses that attackers, auditors, and customers can find without any access to your internal network. Its page evidence groups four areas: DNS and email security checks, SSL monitoring, open port visibility, and CVE mapping. Here is what each covers and what it means in practice.
DNS and email security
ThreatPort checks DNS records and flags missing SPF and DMARC records. Those two omissions are the usual enablers of email spoofing: without SPF, receiving mail servers cannot verify which hosts may send for your domain; without DMARC, you have no published policy telling them what to do with failing mail, and no reporting back to you. A practical first use is to run a free domain scan on your primary sending domain, then check whether your marketing, transactional, and HR systems are all included in SPF before you tighten DMARC.
SSL and certificates
The platform monitors SSL, so expect detection of certificate problems such as expired or soon-to-expire certificates, misconfigured or weak configurations, and certificates on hosts you may not have inventoried. Certificate expiry is the classic self-inflicted outage and a phishing signal; continuous monitoring matters more than a one-off scan because certificates rotate on their own schedule.
Open ports and exposed services
Open port visibility shows which services are reachable from the public internet, along with weak HTTP security headers. This is where the concrete risk usually sits: an accidentally internet-facing admin panel, database port, or remote-access service is a direct path in, and missing headers like HSTS or a content security policy widen browser-side exposure. Pair this with CVE mapping, which links discovered technologies to known vulnerabilities, so you can rank by exploitability rather than by count.
How the pieces fit together
ThreatPort presents these as one continuous, agentless, self-serve workflow: a free domain scan discovers subdomains, exposed services, header weaknesses, missing SPF or DMARC, certificate issues, and technologies tied to known CVEs, with the paid plan adding continuous monitoring, deeper analysis, AI pentest output, and PDF-ready reporting. The audience named on the page is IT managers, CISOs, CTOs, and lean security teams who need evidence for remediation, leadership updates, and compliance preparation without an enterprise sales cycle.
As a decision criterion: if you only need to know your exposure once, a free scan is enough; if certificates, subdomains, and cloud-hosted services change monthly, continuous monitoring is the feature that earns its place, since a stale asset list is how forgotten hosts become breaches. Start by scanning your main domain and comparing the subdomain list against your own inventory — the gap is your real starting point. For context on how exposed services are commonly exploited, see CVE Program and OWASP.
User reviews (0)