Enter a URL
Need to check the DNS records of your website? Free SEO Pro's Find DNS Records tool has a URL input for researching information about a domain. DNS records can facilitate the resolution of domain names to web servers, email and other Internet services and systems. DNS lookups can be used by website owners, developers, and SEO to troubleshoot connectivity issues, check configurations or prepare for a site migration. When you understand the results, you can easily see what possible issues might be occurring, without altering any important settings unnecessarily.
Find DNS Records is a domain query tool designed to help the users to explore Domain Name System records.
The Free SEO Pro page features an "Enter a URL" field. It also contains links to other domain research tools. Its full results page interface has not been documented publicly up to now, the page just showcases explanatory material that was placed as placeholders while the website was under development.
Free Seo Pro
DNS records are instructions that are published via authoritative DNS servers. They provide the requesting systems with information on where to obtain specific services that a domain offers.
DNS lookup can be utilized to explore any site addresses, email routing, domain authentication and other things.
A domain name is a lot more memorable than a numerical IP address.
DNS enables applications to find technical information that is associated with that name.
Bad DNS records can make it difficult for visitors to visit a website or make the email delivery problematic.
But, successful DNS resolution does not mean that a web site is operating properly.
DNS lookup is a request to the Domain Name System for information pertaining to a specific hostname.
The answer is dependent on the record type requested, the records which are available, and the configuration of the resolver.
Different services may sometimes present different information – DNS resolvers can have a memory of previous responses.
Record Main purpose
A Associates an ip address (IPV4) with a hostname
Maps a hostname to an IPv6 address
MX Requests a list of mail exchange servers
NS Lists authoritative nameservers - used to look them up.
TXT Stores text based information.
CNAME Maps one name to another ‘standard’ name
SOA Administrative Information for a DNS Zone (domain)
CAA Indicates which certificate authorities are allowed
Not all record types have to be included in a website.
It can be configured based on the service(s) being used.
TTL stands for Time to Live.
This indicates to a caching resolver that a DNS response might be stored in a normal and natural state for a certain period of time.
In other words, if a TTL is 300 seconds, the record can be cached for 5 minutes in general.
The situation is that in reality visibility of an update is dependent upon the behaviour of a resolver, upon previously stored values in a cache, and upon authoritative configuration.
On the visible page there is an entry field for the URL. The below "howto" is a mixture of that verified input and the usual DNS lookup "workflow".
Click the Find DNS Records page.
To determine your target domain to study.
Duplicate its public hostname, for example, example.com.
Find the box that says 'Enter a URL'
Type in the address of host or supported website.
Make a request to read a value from the look-up that is provided.
Check any DNS records that are returned.
Determine what records are of relevance in your investigation.
Compare important values with your DNS provider's settings.
Recycle the look after enrolled modifications to configuration are performed.
The label on the actual button and the record filters present are yet to be confirmed independently.
The root domain and its subdomains can have different DNS records.
So if example.com does and www.example.com doesn't, then the latter is not being used.
With troubleshooting, confirm that the hostname that is having issues is the correct hostname.
Do not add password, access code or private data to any URLs submitted.
Suppose you're transferring a business site to another web hosting provider.
Your new provider provides you with an IPv4 address and you must check to make sure the domain is pointing to the address.
The following Hypothetical DNS Configuration may look like this:
Record Example value
A 192.0.2.10
MX mail.example.com
TXT v=spf1 -all
NS ns1.example.net
These values are approximate. The domain address used is an ipv4 address and is not a valid host point.
The A record is used for resolving an address for your website.
In the 'MX record' example, a mail exchange destination is identified, and in the ‘TXT’ example, an SPF policy is defined to allow no sending servers.
The NS value is an NS record which stands for a name service.
If you are going to update any records, check the proposed changes against the directions provided by your hosting and email hosts.
These records resolve hostnames to an IPv4 or IPv6 address.
When a website is built on a distributed infrastructure or is load balanced, multiple addresses might be displayed.
A CDN also has the ability to return addresses that are part of their network.
MX records indicate who will receive the email you send to a domain.
These comprise of preference values (also known as priorities).
Smaller preference numbers mean that delivery attempts have a higher priority.
Even if the site is accessible, an incorrect MX setting will cause problems with receiving emails.
Domain verification and email authentication can be done through TXT records.
Massively Distributed environments mostly share SPF policies in the form of TXT records. UTF-8 and DMARC policies both rely on DNS TXT records, as well as DKIM public keys.
Their existence does not necessarily mean that email authentication is set up properly.
The CNAME serves to make an alias from hostnames.
NS records are used to specify authoritative nameservers for a DNS zone or delegation.
Renaming nameservers may have an impact on the overall domain name DNS administration, thus take special care of the destination.
Check against the public address for the domain with the instructions provided by the new provider.
Please note that responses from last year may show up for awhile.
Review MX records and settings.
Other events that can cause email delivery issues include server configuration, lack of authentication, and restrictions by the email service provider.
DNS lookups can be used to check if the hostname is resolving to expected address.
When there is resolution without load of the web page, check the HTTP responses, TLS certificates, and server availability.
Make sure to capture value data before anything happens.
Good to have in place as a backup if one of your previous configurations is needed to be restored.
Common error: Verifying the incorrect hostname. One is assuming that if there is a successful DNS response, the website must be online.
If no records are shown then verify the spelling, nameserver config, and record type asked for.
Variations in the result may be due to caching, geographic routing or recent changes.
If there is any serious issue, check different resolvers and take guidance from the effective DNS provider.
If there are records you don't know the meaning of, never delete them. To remove mail authentication or verification records can cause disruption to other services not connected to your site.
The DNS checker cannot verify the ownership of a website, a site's security, search ranking, or availability of services.
Selected records may only be available in public lookups. Some data may vary from network to network or be cached.
Additional verification is needed for the supported record types, look-up limits, export options, back-end provider, pricing details and data retention of Free SEO Pro.
To learn more about DNS resource record types, refer to the Cloudflare DNS record guide and RFC 1035, which describes the DNS standards.
Domain into IP is a tool to find out addresses behind a website's domain names.
From the Domain Hosting Checker learn whatever you can about potential hosting structure.
Whois Checker offers Registration Information - not DNS Configuration.
If after DNS it's still not clear that the website is accessible, please try the Server Status Checker!
These tools are used in response to varying questions. When mixed, the results give a bit more information for troubleshooting than does using only one look-up.
DNS records checker explores information published by the domain names. It can list web site addresses, nameservers, e-mail routing and verification records based on its capabilities.
Type the Domain into a DNS Lookup Tool and click make sure –> Check the records and look at key values in relation to your DNS provider's configuration.
An A record is used to map a host name to an IP v4 address. It assists clients to identify a network destination, dependent upon proxies and CDNs.
An AAAA record is a configuration that has an IPv6 address to a host name. Both A and AAAA records can be published on websites so that clients may have the ability to connect through various web protocols.
MX records are used to designate domain mail exchange servers. Even if website address records are functioning properly, incorrect MX settings can have a negative impact on incoming email.
TXT Records are used for publishing text information in DNS. Common uses include email authentication policies like SPF, DKIM and DMARC and domain verification.
A CNAME Record is an alias of a hostname. Fortunately, it is widely used for subdomains and some third-party services configurations.
Nameservers contain authoritative information that defines a domain or delegated zone. The location from which resolvers get the published records depends on their configuration.
This can be due to a few reasons such as incorrect hostnames, missing records, nameserver, caching or perhaps transient failure in the name lookup. Use an independent DNS provider lookup to compare with the lookups provided by your DNS provider.
Changes can be readily apparent, while "cached responses" may stay around depending upon settings and resolver behaviour. No single time of update around the world.
When DNS is not set up correctly, people and search bots cannot access the sites. But, records involved can't definitely mean better ranking or quick indexing.
Generally, one doesn't need to be the owner of a domain to retrieve DNS records, if they are publicly published. Infrastructure and user settings that are not published cannot be retrieved using a standard DNS query.
Can show the IP addresses or network services but the origin provider might be hidden due to CDNs or proxies. Only DNS results can not be used in a reliable manner to determine hosting ownership.
No this is not the same test for DNS resolution as it is for website availability. It is possible for a domain to resolve correctly even though the web server is either unavailable or throwing errors.
Test the outcomes against your desired set up, investigate any unexpected values, and ensure that the site/email works. Only make modifications using authorized DNS administration controls.
