dnswatchdog.iodocs

Records

View and manage all DNS records synced from your providers — filter by type, zone, or status, review scan results, archive stale records, and investigate security issues.

Open Records →

Records are the core of the DNS inventory. Each record represents an individual DNS entry (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, etc.) within a zone. Records are the primary target for security scanning — they are scanned for open ports, HTTP behaviour, SSL certificates, and subdomain takeover risks.

Records also carry ISP geolocation data for their resolved IP addresses and can have screenshots captured for visual verification of web endpoints.

The Records table showing DNS records with columns for name, type, value, zone, and status

Record classifications

DNS Watchdog automatically classifies certain records:

  • Verification records — TXT records used for domain ownership verification (e.g. Google, Microsoft)
  • DKIM records — TXT records containing DKIM public keys
  • SPF records — TXT records containing SPF policies
  • DMARC records — TXT records containing DMARC policies
  • Provider nameservers — NS records pointing to the hosting provider's nameservers
  • DNS redirects — records that implement HTTP redirects via the DNS provider

Key fields

FieldDescription
NameThe record name (e.g. www, @, mail)
FQDNFully qualified domain name (e.g. www.example.com)
Record TypeDNS record type: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, etc.
ValueThe record value — IP address, hostname, or text content
TTLTime-to-live in seconds
Priority / Weight / PortAdditional fields for MX and SRV records
ClassificationAuto-detected classification (see list above)
Read-OnlyWhether the record can be modified through DNS Watchdog

Scan results

Each record is scanned automatically during daily scans. The following fields are populated from scan results:

FieldDescription
Port Scan Statuspending, completed, or failed
Open PortsList of open TCP ports detected on the resolved IP
Services DetectedServices identified on open ports (e.g. nginx, Apache, OpenSSH)
HTTP Status CodeResponse code from the HTTP probe (e.g. 200, 301, 404)
HTTP Final URLThe final URL after following all redirects
HTTP Redirect ChainFull chain of redirects followed during the HTTP probe
Certificate Scan StatusWhether SSL certificate analysis has been performed
CertificateLink to the associated certificate if the record serves HTTPS

ISP and geolocation

For A and AAAA records, DNS Watchdog resolves the IP address and performs an ISP lookup to provide network context:

FieldDescription
Resolved IPThe IP address the record resolves to
ISPInternet Service Provider name (e.g. "Amazon.com, Inc.", "Cloudflare, Inc.")
ISP OrganisationOrganisation name registered with the ISP — may differ from the ISP name
ISP AS NumberAutonomous System number identifying the network (e.g. AS16509 for Amazon)
ISP CountryCountry where the IP is geolocated (e.g. "United States", "Germany")
ISP RegionRegion or state within the country (e.g. "Virginia", "Bavaria")
ISP CityCity where the IP is geolocated (e.g. "Ashburn", "Frankfurt")

This data helps you understand where your infrastructure is hosted and identify unexpected geographic distribution.

Screenshots

For records that respond on port 80 or 443, DNS Watchdog captures a screenshot of the web page:

FieldDescription
ScreenshotFull-size screenshot of the web page served at this record's FQDN
ThumbnailSmaller preview image used in list views
Canonical RecordWhen multiple records resolve to the same content, screenshots are deduplicated — this links to the canonical record

See Screenshots for more details on how screenshots are captured and analysed.

Associated issues

Records can have issues from several categories. Here are the most common:

Port exposure

Open ports on the resolved IP address are flagged based on the service type:

HTTP issues

DNS issues

IssueSeverity
Dangling SubdomainCritical
Broken DelegationCritical
Delegated SubdomainWarning

Email security

Actions

  • Archive — soft-delete a record (can be restored from the Archive page)
  • Rescan — trigger a manual rescan of the record's ports, HTTP, and certificates
  • Bulk delete — archive multiple records at once
  • Bulk rescan — rescan multiple records at once

Common tasks

How do I find records for a specific zone?

Use the zone filter in the sidebar or filter controls to narrow the records list to a single zone. You can also navigate to the zone's detail page and view its records from there.

How do I identify stale or unused records?

Look for records with these indicators:

  • HTTP 404 or connection errors — the target may no longer exist
  • Inactive IP issues — the resolved IP has no open ports
  • Dangling subdomain issues — the CNAME target no longer resolves

Sort by issue count to surface records with the most problems.

How do I archive a record?

Select one or more records using the checkboxes, then click Archive. The records are removed from your DNS provider and moved to the Archive page where they can be restored if needed. This requires a read-write provider connection.

How do I find records pointing to decommissioned infrastructure?

Filter by IP address or ISP to find records pointing to specific hosts. Records pointing to IPs with no open ports (flagged with the "Inactive IP" issue) are likely candidates for cleanup.

On this page