Skip to main content

Remediation Workspace

Get copy-paste-ready DNS records to fix your domain security issues.

Enter the domain you want to fix.

OR
Or enter a specific scan number from your analysis history.

How It Works

1

Scan your domain to identify security gaps

2

Copy the exact DNS records from this page

3

Paste into Cloudflare, GoDaddy, or your DNS provider

Remediation: freebsd.org

Scan #19506 · 18 Nov 2026, 04:20 UTC · Achievable posture: Low Risk

2 remediation items found. Click any record value to copy it to your clipboard, then paste it into your DNS provider.

Provider Quick Guide

  1. Log in to dash.cloudflare.com and select your domain
  2. Go to DNS → Records
  3. Click Add Record
  4. Select the Type shown below (TXT, CNAME, MX, etc.)
  5. Paste the Name (host) and Content (value) from each card below
  6. Set Proxy status to DNS only (grey cloud) for email records
  7. Click Save
  1. Log in to dcc.godaddy.com
  2. Select your domain, then click DNS (or Manage DNS)
  3. Scroll to DNS Records and click Add New Record
  4. Select the Type shown below
  5. In Name, enter the host (use @ for the root domain)
  6. In Value, paste the record value from the card below
  7. Click Save
  1. Log in to your DNS hosting provider's control panel
  2. Navigate to DNS Management or Zone Editor
  3. Add a new record with the type, host, and value shown in each card below
  4. For the host field, use @ if your provider requires it for the root domain
  5. Save and allow up to 24–48 hours for propagation (usually much faster)

Manual Configuration Steps

High Real Fix — exploitable_now DMARC Policy Enforcement

DMARC policy is not set to reject. Per RFC 7489 §6.3, only p=reject instructs receivers to discard unauthenticated messages. NIST SP 800-177 Rev. 1 §4.6.1 recommends reject for all production domains. Exploitability: Sender / identity spoofing requires no privileged position: an attacker forges mail or impersonates the domain with off-the-shelf tooling (CWE-290 / CAPEC identity-spoofing patterns). Blast radius: Customers, partners and brand: recipients are phished using the domain's identity. Confidence: Directly observed DNS records (ICIE Tier 1 evidence); verdict determinate. Weakness mapping verified at high confidence (CWE/CAPEC/VRT).

Medium Real Fix — exploitable_now SPF Effective Authorization Policy

SPF policy is permissive without DMARC enforcement. SPF softfail (~all) without DMARC p=reject or p=quarantine leaves email authorization unenforced. Per RFC 7489, DMARC provides the enforcement layer that makes SPF softfail operationally effective. Either tighten SPF to -all or deploy DMARC with an enforcement policy. Exploitability: Sender / identity spoofing requires no privileged position: an attacker forges mail or impersonates the domain with off-the-shelf tooling (CWE-290 / CAPEC identity-spoofing patterns). Blast radius: Customers, partners and brand: recipients are phished using the domain's identity. Confidence: Directly observed DNS records (ICIE Tier 1 evidence); verdict determinate. Weakness mapping verified at medium confidence (contributory control).

Done making changes?

After updating your DNS records, run a new scan to verify everything is correct. DNS changes typically propagate within minutes, but can take up to 48 hours.

Re-Scan freebsd.org
Straight talk about your data.

We use two cookies, both essential:

  • _csrf — Prevents cross-site request forgery. Required for form submissions. Security-only.
  • _dns_session — Only exists if you choose to sign in. No account required to use DNS Tool.

We log your IP address for two reasons: rate limiting (so nobody abuses the service) and security (identifying malicious actors and complying with legal obligations). We check source geography for analysis accuracy — DNS responses vary by region, and knowing which resolver answered from where makes the science better.

No tracking cookies. No analytics cookies. No ad networks. No data brokers. Our code is open-core — the application framework is publicly available under BUSL-1.1 with timed Apache-2.0 conversion. Verify it yourself.

Public analyses are archived by a third party. When a scan is not marked private or run as /dev/null, its report URL is submitted to the Internet Archive, which creates a permanent public record outside our control. That is deliberate — it gives every published analysis tamper-evident provenance independent of us — but it is not reversible, so it is stated here before you scan rather than after.

If you create an account and want out, account deletion removes your login and scan history. Public domain analyses remain available because they contain only public DNS records, already hashed. Full details: Privacy Policy.