Trace report companion

Understanding your Trace report

A plain-language guide to what each item in your report actually checks, why it matters, and what to do about it. Meant to sit alongside the report itself, not replace a conversation with whoever manages your website, email, or IT. Every question below is worded exactly as it appears in your report's Check column.

Not everything is a problem

Some entries exist purely to document evidence: how we found your assets, or background context. These are tagged Context only and carry no action item.

The tags aren't a score

High priority deserves attention sooner rather than later. Very few items here are drop-everything emergencies. Read this as a prioritised list, not an alarm.

How these tags relate to your report: when a High priority check fails, it appears in your report as High. Worth addressing appears as Medium, Tidy up and Optional cleanup as Low, and Context only as Informational. Depends on the detail items don't have one fixed severity: what you see in your report depends on what's actually found.

You don't fix this alone

For almost everything below, the right move is a short conversation with whoever already manages that part of your setup. Not sure who? Get in touch and we'll point you the right way.

Email Security

14 checks

Does the domain publish an SPF record at all?

High priority
What it means

SPF is a published list of which mail servers are allowed to send email on your domain's behalf. This checks whether that list exists at all.

Why it matters

Without it, there's no authoritative way for anyone receiving mail to tell your real emails apart from someone forging your domain; there's simply nothing to check against.

Recommended next step

Ask whoever manages your domain's DNS (often your web host, IT provider, or email platform) to set up an SPF record for your domain.

Does the SPF record's trailing mechanism reject or merely flag unlisted senders?

Tidy up when convenient
What it means

Beyond just existing, an SPF record can either firmly reject unauthorised senders or merely flag them as suspicious without blocking anything.

Why it matters

A weak policy still leaves the door open: receiving mail servers are told “this looks off” but not “reject this,” so forged mail can still land in inboxes.

Recommended next step

Ask whoever manages your SPF record to tighten its enforcement setting once you're confident all your legitimate mail sources are correctly listed.

Does the SPF record's evaluation chain exceed RFC 7208's 10-DNS-lookup limit?

High priority
What it means

SPF records have a technical limit on how many DNS lookups they can trigger during evaluation. This checks whether yours has grown past that limit.

Why it matters

Once the limit is exceeded, most mail servers treat your entire SPF setup as broken and ignore it completely, silently undoing whatever protection you thought you had, often without anyone noticing.

Recommended next step

Ask whoever manages your SPF record to review and simplify it. This is common on domains that use several different email or marketing tools.

Does the domain publish more than one SPF-shaped TXT record?

High priority
What it means

A domain should publish exactly one SPF record. This checks whether more than one exists.

Why it matters

Having more than one makes the whole thing invalid by definition, which (like exceeding the lookup limit) quietly disables your SPF protection entirely.

Recommended next step

Ask whoever manages your DNS to consolidate all your sending sources into a single SPF record.

Does the domain publish a DMARC record at all?

High priority
What it means

DMARC builds on SPF and tells receiving mail servers what to do when a message fails those checks, and gives you visibility into who's sending mail using your domain. This checks whether a DMARC record exists.

Why it matters

Without DMARC, you have no policy in place and no reporting, so you'd have no visibility if your domain were ever being spoofed.

Recommended next step

Ask whoever manages your DNS or email platform to set up a DMARC record. Most providers offer guided setup for this.

Does the DMARC policy actually instruct receivers to act on failures?

Worth addressing
What it means

A DMARC record can be set to only monitor spoofing attempts, or to actively instruct receivers to quarantine or reject fraudulent mail.

Why it matters

A monitoring-only policy gives you visibility but doesn't actually stop anything: spoofed mail using your domain can still reach its target.

Recommended next step

Once you've reviewed DMARC reports and are confident it's safe to do so, ask whoever manages this to move toward an enforcing policy.

Is DMARC aggregate reporting (rua=) configured at all?

Tidy up when convenient
What it means

DMARC can send you a regular summary of who's sending mail claiming to be from your domain. This checks whether that reporting address is configured.

Why it matters

Without it, DMARC is running blind: even if it's technically active, nobody is actually seeing whether spoofing attempts are happening.

Recommended next step

Ask whoever manages your DMARC record to add a reporting address so this visibility isn't going to waste.

Is the DMARC record structurally valid enough to evaluate reliably?

Worth addressing
What it means

Checks whether your DMARC record is written correctly enough for mail servers to reliably interpret it.

Why it matters

A record with structural problems may be partially or entirely ignored by receiving servers, which can quietly undercut protection you believe is in place.

Recommended next step

Ask whoever manages your DMARC record to review and correct its formatting.

Does mail sent from this domain carry a DKIM signature, checked against common selectors?

Worth addressing
What it means

DKIM digitally signs outgoing mail so receivers can verify it genuinely came from your systems and wasn't altered in transit.

Why it matters

Without a valid DKIM signature, receiving mail servers have one less way to distinguish your legitimate mail from a forgery, and some providers will flag or reject unsigned mail more aggressively.

Recommended next step

Ask your email provider (e.g. Google Workspace or Microsoft 365) to enable DKIM signing. Most providers support this natively.

Does the domain publish an MTA-STS policy (_mta-sts.<domain> TXT record)?

Tidy up when convenient
What it means

MTA-STS is a stronger commitment that mail sent to your domain must always use encrypted transport, closing a loophole where an attacker could otherwise silently downgrade a connection to unencrypted.

Why it matters

Without it, encryption in transit is only “best effort,” and a well-positioned attacker on the network path could strip it away without either side noticing.

Recommended next step

This is a more advanced control most organisations haven't adopted yet. Ask your email provider or IT provider whether it's supported and worth enabling for your setup.

Does the domain publish a TLS-RPT reporting address (_smtp._tls.<domain> TXT record)?

Tidy up when convenient
What it means

TLS-RPT gives you visibility into cases where a sending server couldn't establish an encrypted connection to your mail servers.

Why it matters

Without it, encryption failures could happen silently: you'd have no way to know if something's misconfigured or being tampered with.

Recommended next step

Ask your email or IT provider whether this can be enabled alongside MTA-STS above.

If the DMARC rua= destination is on an external domain, does that domain publish the required authorization record?

Tidy up when convenient
What it means

If your DMARC reports are sent to a third-party address (a monitoring service, for example), that third party needs to explicitly authorise receiving reports about your domain.

Why it matters

Without that authorisation, your DMARC reports are silently dropped by receiving mail servers, and you'd assume you're getting visibility into spoofing attempts when you actually aren't.

Recommended next step

Ask whoever manages your DMARC reporting service to confirm the authorisation record is correctly published.

What mail servers does this domain route inbound mail to?

Context only
What it means

This lists which mail servers your domain routes incoming email through. It's evidence, not a verdict.

Why it matters

It's included so the assessment record shows exactly what mail infrastructure was in scope, useful context if you're reviewing your setup with your IT provider.

Recommended next step

No action needed. Worth a glance to confirm it matches what you expect.

Does the domain's mail server(s) support opportunistic transport encryption (STARTTLS)?

Worth addressing
What it means

Checks whether your mail servers support encrypting the connection when receiving email, rather than accepting it in plain text.

Why it matters

Without it, email content could potentially be read by someone in a position to intercept network traffic between mail servers: a confidentiality risk, distinct from the spoofing risks above.

Recommended next step

Ask your email/IT provider to confirm encrypted transport is enabled on your mail servers.

Takeover Risk

2 checks

Does any MX host still resolve, or is mail routed to a dangling hostname a third party could reclaim?

High priority
What it means

The mail-routing equivalent of the check above: whether a mail server your domain lists still exists, or points at a dangling resource someone else could claim.

Why it matters

A takeover here could let someone intercept or receive email intended for your organisation.

Recommended next step

If flagged, this needs prompt attention. Ask whoever manages your DNS/mail routing to review and remove the dangling entry.

Does any discovered hostname's CNAME point to a third-party service resource that has been deprovisioned/unclaimed, allowing an attacker to claim it and serve content on the client's own subdomain?

High priority
What it means

Checks whether any of your subdomains point to a third-party service (like a hosting or app platform) that has since been deleted or deprovisioned, leaving that address available for anyone to claim.

Why it matters

If confirmed, someone else could register that abandoned resource and immediately start serving their own content (including phishing pages) from what looks like a legitimate address on your domain.

Recommended next step

If this is flagged as a real risk, this needs prompt attention. Ask your IT provider or whoever set up that subdomain to either remove the unused DNS entry or reclaim the resource.

Certificates

4 checks

Does the TLS certificate served on a hostname actually cover that hostname (CN or SAN)?

High priority
What it means

Checks whether the certificate actually served on a given address covers that address by name.

Why it matters

A mismatch means every visitor gets a hard security warning in their browser before they can even reach your site, and it also often points to a bigger underlying misconfiguration.

Recommended next step

This needs attention soon. Ask your web hosting provider or IT team to correct the certificate assigned to this address.

Is the certificate's validity period within the current CA/Browser Forum maximum, and if not, how far out of date is the issuance policy it reflects?

Depends on the detail
What it means

Certificate authorities are only allowed to issue certificates valid for a certain maximum length of time, and that maximum has gotten stricter over the years. This checks whether your certificate was issued under an outdated, looser policy.

Why it matters

A certificate issued far outside current rules is often a sign it's self-signed, from an internal system, or long overdue for renewal. Worth a second look rather than an emergency.

Recommended next step

Ask your hosting provider to confirm the certificate is due for a standard renewal.

How many days remain until the certificate actually expires?

Depends on the detail
What it means

How many days remain before this specific certificate actually expires.

Why it matters

An expired certificate breaks secure access to your site entirely for visitors, showing a blocking warning rather than just a cosmetic issue.

Recommended next step

If this is inside the warning window, ask your hosting provider to renew it promptly. Most modern setups renew automatically, so this is also worth confirming that auto-renewal is actually working.

Does the served certificate chain actually validate against a standard trust store?

High priority
What it means

Checks whether the certificate your site presents can actually be verified against the standard certificate authorities that browsers trust.

Why it matters

If it doesn't validate, every visitor sees a hard security warning: the same practical impact as a hostname mismatch, just a different underlying cause (commonly a missing piece of the certificate chain, or an untrusted/self-signed certificate).

Recommended next step

This needs attention soon. Ask your hosting provider to check the certificate installation, particularly whether an intermediate certificate is missing.

Web Hardening

15 checks

Does the site send a Strict-Transport-Security header, and how resilient is it?

Depends on the detail
What it means

This header tells browsers to always use an encrypted connection to your site, even if someone types or links to the plain, unencrypted version.

Why it matters

Without it, there's a brief window on a user's very first visit where a network attacker could intercept an unencrypted connection before it upgrades to HTTPS.

Recommended next step

Ask your website developer or hosting provider to enable this header, and to set a strong enough duration if it's already present but weak.

Is the domain on the browser HSTS preload list?

Context only
What it means

Beyond the header above, browsers maintain a built-in list of sites that should always load securely, even before the browser has ever visited them. This simply reports whether your domain is on that list, informational only.

Why it matters

It's a nice-to-have hardening step, not a gap in itself. Most organisations haven't done this.

Recommended next step

No action typically needed. If you want to pursue it, your website developer can walk you through submission.

Does the site send a Content-Security-Policy header, and if so, is it permissive?

Tidy up when convenient
What it means

CSP is a header that restricts which sources of content (scripts, images, etc.) a browser is allowed to load on your site.

Why it matters

Without it, if an attacker ever manages to inject malicious code into your site (for example through a vulnerable plugin), there's nothing stopping that code from running freely.

Recommended next step

Ask your website developer to implement a Content Security Policy appropriate to your site.

Does the site send an X-Frame-Options header (or equivalent CSP frame-ancestors)?

Tidy up when convenient
What it means

Checks whether your site prevents itself from being loaded inside an invisible frame on someone else's page.

Why it matters

Without this protection, an attacker could overlay your site inside their own page to trick visitors into clicking something they didn't intend to: a technique called clickjacking.

Recommended next step

Ask your website developer or hosting provider to add this header.

Does the site send X-Content-Type-Options: nosniff?

Tidy up when convenient
What it means

Checks for a header that stops browsers from trying to “guess” a file's type differently from what the server declared.

Why it matters

Without it, a browser might interpret an uploaded file (like an image) as executable content, opening a route for malicious file uploads to cause more damage than intended.

Recommended next step

Ask your website developer to add this header. It's typically a very quick configuration change.

Does the site disclose its backend framework via X-Powered-By or similar?

Optional cleanup
What it means

Some servers announce the exact framework or software version powering the site.

Why it matters

This makes it slightly easier for an attacker to look up known vulnerabilities for your specific software version. It's a minor information leak, not a vulnerability on its own.

Recommended next step

Optional cleanup. Ask your website developer to suppress this header when convenient.

Does the site disclose its web server software via the Server header?

Optional cleanup
What it means

Similar to the above, but for the underlying web server software itself rather than the application framework.

Why it matters

Same reasoning as above: minor reconnaissance value for an attacker, not a direct risk.

Recommended next step

Optional cleanup. Ask your hosting provider to suppress this header when convenient.

Does the site send a Permissions-Policy header restricting browser feature access (camera/mic/geolocation/etc.)?

Tidy up when convenient
What it means

This header lets a site explicitly restrict which browser features (camera, microphone, location, etc.) it or anything embedded in it can access.

Why it matters

Without it, any script running on your page, including from a third-party embed, has unrestricted access to request these sensitive browser permissions.

Recommended next step

Worth raising with your website developer, though this is still an uncommon control even on well-secured sites.

Does the site send a Referrer-Policy header, and if so, does it avoid leaking full URLs to other origins?

Tidy up when convenient
What it means

Checks whether your site is explicitly configured to leak full page URLs (which can include sensitive query information) to other sites when a visitor clicks a link away from yours.

Why it matters

If explicitly misconfigured this way, sensitive information embedded in your URLs could be exposed to third-party sites your visitors click through to.

Recommended next step

If flagged, ask your website developer to correct this setting. Most sites don't need to change anything, as modern browsers already default to a safe behaviour.

Does the site publish a security.txt file (RFC 9116) for responsible-disclosure contact?

Optional cleanup
What it means

This checks whether your site publishes a standard file telling security researchers how to responsibly report a vulnerability they find.

Why it matters

Not having one isn't a gap: most sites don't. Having one is a positive, proactive signal.

Recommended next step

Optional. If you'd like to make it easier for researchers to report issues to you responsibly, your website developer can add this in a few minutes.

Does plain HTTP redirect to HTTPS, and stay on HTTPS for the rest of the redirect chain?

Worth addressing
What it means

Checks whether visiting your site over the old, unencrypted address automatically and reliably redirects to the secure version.

Why it matters

If it doesn't, or drops back to the unencrypted version partway through, visitors who type your address without “https://” could end up on an unprotected connection without realising it.

Recommended next step

Ask your hosting provider or website developer to review and fix the redirect configuration.

Does the server accept obviously weak/deprecated TLS ciphers (RC4, single/triple-DES, export-grade, NULL encryption, MD5 MAC)?

High priority
What it means

Checks whether your server will still accept old, broken encryption methods if asked, rather than only offering modern, secure ones.

Why it matters

Accepting these older methods gives an attacker in a strong network position a route to weaken the connection's security. This needs attention soon.

Recommended next step

Ask your hosting provider to disable legacy cipher support on your server.

Does the server accept a TLS 1.0 or TLS 1.1 handshake (both deprecated by RFC 8996)?

High priority
What it means

Similar to the above but at the protocol level: checks whether your server still accepts the two oldest, officially deprecated versions of TLS encryption.

Why it matters

These versions have known weaknesses and are also often required for compliance standards (such as PCI-DSS) to be disabled. This needs attention soon.

Recommended next step

Ask your hosting provider to disable TLS 1.0 and 1.1, leaving only modern TLS versions enabled.

Does the server reflect an arbitrary Origin header unconditionally in Access-Control-Allow-Origin, or return an unrestricted wildcard?

Worth addressing
What it means

CORS controls which other websites are allowed to make requests to yours from a visitor's browser. This checks whether your site is configured to allow literally any website to do so, without restriction.

Why it matters

An overly permissive policy, if it also lets those requests carry a visitor's login cookies, can let a malicious site quietly act on their behalf.

Recommended next step

Worth a conversation with your website developer, particularly if your site has any logged-in or authenticated areas.

Do cookies set by the site carry Secure, HttpOnly, and SameSite attributes?

Tidy up when convenient
What it means

Checks whether cookies your site sets are marked to only travel over encrypted connections and to be inaccessible to page scripts.

Why it matters

Without these attributes, cookies (which often carry session/login information) are more exposed to interception, theft via malicious scripts, or being sent along with requests triggered by other sites without the visitor's intent.

Recommended next step

Ask your website developer to review and add the missing attributes to your site's cookies.

Exposure

6 checks

Are well-known sensitive paths (.git, .env, backup files, credential files) exposed?

High priority
What it means

Checks whether commonly-targeted sensitive files (like configuration files, backup files, or version control folders) are accidentally publicly accessible on your website.

Why it matters

If any of these are exposed, this is a direct, no-further-effort-required disclosure: it can include source code, credentials, or infrastructure details in a single request. This needs prompt attention.

Recommended next step

Ask your website developer or hosting provider to remove or restrict access to any exposed files immediately.

Are debug/management interfaces (Spring Actuator, metrics, phpinfo) exposed?

High priority
What it means

Checks for developer or admin tools (like application debugging dashboards) that were left accessible to the public internet.

Why it matters

These interfaces are often built assuming only trusted internal users would ever reach them, so they frequently disclose configuration details or internal data with no authentication required. This needs prompt attention.

Recommended next step

Ask your website developer to restrict access to any exposed debug or admin tools immediately.

Do cloud storage buckets/containers matching common naming conventions for this organisation exist, and are they publicly listable?

High priority
What it means

Checks whether cloud storage (like an AWS, Azure, or Google Cloud storage bucket) matching your organisation's naming pattern exists and is set to allow anyone to list its contents.

Why it matters

A publicly listable bucket can mean anyone can browse and potentially download whatever's stored there. This needs prompt attention if confirmed.

Recommended next step

Ask whoever manages your cloud infrastructure account to review and lock down access permissions immediately.

Does the site's own published JavaScript contain hardcoded API keys or secrets?

High priority
What it means

Checks your website's published code for strings that look like hardcoded API keys or access credentials.

Why it matters

If found, this is live, usable credential material anyone can extract from your page today, not a theoretical weakness. This needs prompt attention.

Recommended next step

Ask your website developer to remove the credential from the code and rotate/replace it immediately, since it should be considered compromised.

Does the site publish JavaScript source map (.map) files?

Worth addressing
What it means

Source maps are development files that map a website's minified code back to its original, readable source. This checks whether they've been accidentally published alongside the live site.

Why it matters

If exposed, they can reveal your site's internal structure, file paths, and occasionally leftover comments containing sensitive information.

Recommended next step

Ask your website developer to exclude source maps from the production deployment.

What email addresses does the site's own crawled content publish?

Context only
What it means

Lists email addresses found published on your own website. This is background evidence, not a verdict: publishing a contact address is often entirely deliberate.

Why it matters

Included so you have visibility into what's publicly discoverable about your organisation, in case anything unexpected shows up in the list.

Recommended next step

No action needed unless something in the list looks unexpected or out of date.

DNS Hygiene

6 checks

Does a CAA record restrict which Certificate Authorities may issue TLS certificates for this domain?

Tidy up when convenient
What it means

A CAA record lets you specify which certificate authorities are allowed to issue certificates for your domain at all.

Why it matters

Without one, any recognised certificate authority could technically issue a certificate for your domain, which removes one layer of protection against certificate mis-issuance.

Recommended next step

Ask whoever manages your DNS to add a CAA record listing your legitimate certificate provider(s).

Is the domain's DNS cryptographically signed and validating?

Tidy up when convenient
What it means

DNSSEC cryptographically signs your DNS records so they can't be tampered with in transit without detection.

Why it matters

Without it, DNS responses for your domain could theoretically be spoofed or manipulated by an attacker in the right network position, redirecting visitors without any warning.

Recommended next step

Ask your domain registrar or DNS provider whether DNSSEC is supported and can be enabled. Many providers now offer one-click setup.

Does the reverse-DNS (PTR) record for a hostname's IP relate back to that hostname?

Tidy up when convenient
What it means

Checks whether the reverse-lookup record for an IP address (which server owns this address) actually matches the hostname pointing at it.

Why it matters

A mismatch (outside of normal shared cloud hosting patterns) can indicate stale DNS records or an address serving more than one purpose than intended.

Recommended next step

Usually low priority. Ask your IT provider to review if it's flagged as an actual mismatch rather than expected cloud-provider behaviour.

Does any of the domain's own authoritative nameservers also answer recursive queries (i.e. behave as an open resolver), rather than being locked down to authoritative-only?

Tidy up when convenient
What it means

Checks whether your domain's own nameservers will also answer DNS queries for unrelated domains, rather than being locked down to only answer for yours.

Why it matters

An open resolver can be abused by attackers as part of broader internet-scale attacks, and increases exposure to a technique called cache poisoning.

Recommended next step

Ask whoever manages your nameservers to restrict them to authoritative-only mode.

Do any of the domain's authoritative nameservers permit unauthenticated DNS zone transfer (AXFR)?

High priority
What it means

Checks whether your nameservers will hand over your entire DNS zone (every subdomain and internal hostname you've configured) to anyone who asks, without authentication.

Why it matters

If this is enabled, it discloses your complete internal DNS structure in a single request, which is a significant reconnaissance win for anyone probing your organisation. This needs attention soon.

Recommended next step

Ask whoever manages your nameservers to disable unauthenticated zone transfers.

Do all of the domain's authoritative nameservers agree on the domain's own NS record set?

Tidy up when convenient
What it means

Checks whether all of your domain's nameservers agree on which nameservers are actually authoritative for it.

Why it matters

A disagreement is usually a sign of a leftover or partially-migrated nameserver configuration: an operational hygiene issue rather than something actively exploitable.

Recommended next step

Low priority, worth mentioning to whoever manages your DNS next time they're making changes there.

Lookalike Domain Monitoring

3 checks

Are any typosquat/homoglyph permutations of the domain registered with an active mail exchange?

High priority
What it means

Checks for registered domains that look similar to yours (through typos or lookalike characters) and have active mail servers configured.

Why it matters

A lookalike domain with live mail pointed at unrelated infrastructure is a strong signal of active phishing infrastructure being staged against your brand. This needs prompt attention.

Recommended next step

Get in touch with us directly. We can help you assess the risk and, if needed, guide you through reporting or takedown options.

Does any registered lookalike domain's live web page visually match the real site's homepage?

High priority
What it means

Goes a step further than the above: checks whether any registered lookalike domain's live website visually matches your actual homepage.

Why it matters

A visual clone is strong confirmation of an active phishing or credential-harvesting site impersonating you, not just a speculative risk. This needs prompt attention.

Recommended next step

Get in touch with us directly. This is worth escalating quickly, and we can help guide the right response.

What typosquat/homoglyph permutations of the domain are registered, regardless of whether they have live mail?

Context only
What it means

A full list of similar-looking domains that are registered, regardless of whether they show signs of active misuse yet. This is background evidence, not a verdict on its own.

Why it matters

Even a dormant lookalike domain is worth being aware of: it could be parked for a future phishing campaign.

Recommended next step

No immediate action needed, but worth keeping in mind if any of these domains later show signs of activity.

WHOIS / Registration

6 checks

How close is this domain to its registration expiry date?

Depends on the detail
What it means

How close your domain is to its registration renewal date.

Why it matters

If a domain lapses, everything built on it (your website, email, and any other services) goes down immediately, and there's a real risk of someone else registering it once it's available. This needs attention as the expiry date approaches.

Recommended next step

Confirm with whoever manages your domain registration that auto-renewal is enabled, or renew manually before the date approaches.

Does the domain have a registrar transfer lock (clientTransferProhibited or equivalent) set?

Depends on the detail
What it means

Checks whether your domain has a lock in place preventing it from being transferred to another registrar without your explicit action.

Why it matters

Without this lock, if your registrar account were ever compromised, your domain could be transferred away with comparatively little friction.

Recommended next step

.au domains don't offer a registrant-controlled transfer lock, so your report marks this not applicable. For other domains, ask your registrar to confirm transfer lock is enabled.

Is the registrant's WHOIS contact information hidden behind a privacy/proxy service?

Context only
What it means

Reports whether your domain's registration contact details are hidden behind a privacy service, or published openly. This is background context, not a verdict: it's a legitimate business choice either way.

Why it matters

Worth knowing so you can confirm it matches your organisation's actual preference.

Recommended next step

No action needed unless the current setting doesn't match what you'd prefer.

What country is the registrant contact listed in, per WHOIS?

Context only
What it means

Records which country is listed against the domain's registration contact, where published.

Why it matters

Background context only, often absent by default due to modern privacy rules, which is normal.

Recommended next step

No action needed.

Was the WHOIS record updated recently?

Context only
What it means

Reports whether your domain's registration record has been updated recently. This is neutral evidence: a routine renewal and an unauthorised change look identical from this one data point.

Why it matters

It's worth a quick confirmation if you weren't expecting a change, just to rule out anything unexpected.

Recommended next step

If you didn't recently make a change yourself, a quick check with your registrar to confirm nothing unauthorised occurred is a sensible precaution.

Which registrar administers this domain, per WHOIS?

Context only
What it means

Simply records which company administers your domain registration.

Why it matters

Background context for the report, not a finding.

Recommended next step

No action needed.

Discovery Evidence

4 checks

Every item here is tagged Context only: it documents how we found or attributed something, not a pass/fail verdict. Included so nothing is silently omitted, per methodology.

What paths does the site's robots.txt declare disallowed?

Context only
What it means

Lists paths your website's robots.txt file asks search engines not to index.

Why it matters

This file is sometimes the only public hint that an admin or login page exists at a particular address: useful evidence, not a vulnerability on its own.

Recommended next step

No action needed.

What nameservers does this domain delegate to?

Context only
What it means

Lists the nameservers your domain delegates to.

Why it matters

Nameservers are sometimes where a forgotten or orphaned piece of infrastructure's story starts, useful reference if you're auditing your own environment.

Recommended next step

No action needed, but worth a glance to confirm it matches what you expect.

What certificates has Certificate Transparency logged for this domain's hostnames?

Context only
What it means

A history of certificates publicly logged for your domain's various addresses, which is often how additional subdomains were discovered in the first place.

Why it matters

This is the evidence trail behind the discovery process: it shows where some of the addresses covered elsewhere in this report actually came from.

Recommended next step

No action needed.

Which hostnames from a pinned common-infrastructure wordlist actually resolve, beyond what non-intrusive discovery already found?

Context only
What it means

Records any additional addresses found by testing a list of common naming patterns (like “dev.” or “staging.”) against your domain, beyond what was already discovered through other methods.

Why it matters

Sometimes surfaces forgotten test or staging environments that are still live and may not be getting the same security attention as your main site.

Recommended next step

If anything unexpected turns up here, worth confirming with your IT provider whether it's still needed and, if so, that it's properly secured.

Attribution

2 checks

Every item here is tagged Context only: it documents how we found or attributed something, not a pass/fail verdict. Included so nothing is silently omitted, per methodology.

What ASN/organisation owns the IP space this domain resolves to?

Context only
What it means

Identifies which network provider or organisation owns the IP address space your domain resolves to.

Why it matters

Background context that can help confirm your infrastructure is hosted where you expect it to be.

Recommended next step

No action needed.

Does the same organisation appear to own equivalent domains under other regional/generic TLDs?

Context only
What it means

Checks whether your organisation appears to own equivalent domains under other regional or generic extensions (for example, a .com alongside a .com.au).

Why it matters

Purely informational: if a related domain is confirmed and has its own real issues, those would surface separately once it's added to a future assessment's scope.

Recommended next step

No action needed.

Asset Discovery

1 check

Every item here is tagged Context only: it documents how we found or attributed something, not a pass/fail verdict. Included so nothing is silently omitted, per methodology.

How many candidate hostnames were discovered and how many resolve?

Context only
What it means

A summary of how many candidate addresses were discovered during the assessment and how many were confirmed live.

Why it matters

Gives you a sense of the overall scope and thoroughness of the assessment.

Recommended next step

No action needed.