Skip to main content

Remediation: dnstool.it-help.tech

Scan #756 · 14 Feb 2026, 05:28 UTC · Achievable posture: Low Risk

Full Report Re-Scan to Verify
4 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)

DNS Records to Add or Update

Medium mta_sts Deploy MTA-STS policy

Publish an MTA-STS DNS record and host a policy file at https://mta-sts.dnstool.it-help.tech/.well-known/mta-sts.txt. This tells senders to require TLS when delivering mail to your domain.

Record Type
Host / Name
Value / Content
Full record (click to copy)
_mta-sts.dnstool.it-help.tech TXT "v=STSv1; id=20240101"
RFC 8461 §3
Low caa Add CAA records

Publish CAA DNS records to restrict which Certificate Authorities can issue TLS certificates for your domain. Specify your preferred CA (e.g., letsencrypt.org, digicert.com). CAA is advisory — CAs must check it before issuing, but absence means any CA can issue.

Record Type
Host / Name
Value / Content
Full record (click to copy)
dnstool.it-help.tech CAA 0 issue "letsencrypt.org"
RFC 8659 §4
Low dane Deploy DANE/TLSA for email transport

DNSSEC is already enabled — you can strengthen email transport security by publishing DANE TLSA records. DANE binds your mail server's TLS certificate to DNS, preventing man-in-the-middle attacks on SMTP connections.

Record Type
Host / Name
Value / Content
Full record (click to copy)
_25._tcp.mail.dnstool.it-help.tech TLSA 3 1 1 <certificate_hash>
RFC 7672 §3
Low bimi Configure BIMI brand logo

Publish a BIMI DNS record pointing to your brand logo (SVG Tiny PS format). For full support in Gmail, you will also need a Verified Mark Certificate (VMC).

Record Type
Host / Name
Value / Content
Full record (click to copy)
default._bimi.dnstool.it-help.tech TXT "v=BIMI1; l=https://dnstool.it-help.tech/logo.svg"
BIMI Spec

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 dnstool.it-help.tech
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.

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.