Remediation Workspace
Get copy-paste-ready DNS records to fix your domain security issues.
How It Works
Scan your domain to identify security gaps
Copy the exact DNS records from this page
Paste into Cloudflare, GoDaddy, or your DNS provider
Remediation: devontechnologies.com
Scan #18144 · 5 Aug 2026, 09:16 UTC · Achievable posture: Hardened
Provider Quick Guide
- Log in to dash.cloudflare.com and select your domain
- Go to DNS → Records
- Click Add Record
- Select the Type shown below (TXT, CNAME, MX, etc.)
- Paste the Name (host) and Content (value) from each card below
- Set Proxy status to DNS only (grey cloud) for email records
- Click Save
- Log in to dcc.godaddy.com
- Select your domain, then click DNS (or Manage DNS)
- Scroll to DNS Records and click Add New Record
- Select the Type shown below
- In Name, enter the host (use
@for the root domain) - In Value, paste the record value from the card below
- Click Save
- Log in to your DNS hosting provider's control panel
- Navigate to DNS Management or Zone Editor
- Add a new record with the type, host, and value shown in each card below
- For the host field, use
@if your provider requires it for the root domain - Save and allow up to 24–48 hours for propagation (usually much faster)
Manual Configuration Steps
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).
DNSSEC not authenticated — DNS responses for this domain are not cryptographically validated. An attacker positioned between the resolver and authoritative server can forge responses (Kaminsky attack, RFC 5452). Per RFC 4033 §2, "DNSSEC provides origin authentication and integrity assurance." Exploitability: Exploitation requires an on-path or cache-poisoning position against the resolution path (CWE-300/345, CAPEC DNS cache poisoning). Blast radius: Everyone resolving the domain through an affected resolution path. Confidence: Directly observed DNS records (ICIE Tier 1 evidence); verdict determinate. Weakness mapping verified at high confidence (CWE/CAPEC/VRT).
No CAA records found — any Certificate Authority can issue certificates for this domain. Per RFC 8659 §4.2, CAs are required to check CAA records before issuance. Without CAA, misissued certificates cannot be prevented at the DNS layer. Exploitability: No verified weakness mapping yet — exploitability is not asserted. Blast radius: Scope limited to the operator's own posture until a weakness mapping is verified. Confidence: Directly observed DNS records (ICIE Tier 1 evidence); verdict determinate. Standards gap is certain, but the weakness/exploit lineage is not yet verified.
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 devontechnologies.com