No TXT records found for blog.naver.com.
Try naver.com instead?
id 16247, opcode QUERY, rcode NOERROR, flags QR RD RA ;QUESTION blog.naver.com. IN TXT ;ANSWER blog.naver.com. 15443 IN CNAME blog.naver.com.nheos.com. blog.naver.com.nheos.com. 7036 IN CNAME blog.naver.com.edgekey.net. blog.naver.com.edgekey.net. 15258 IN CNAME e6030.a.akamaiedge.net. ;AUTHORITY a.akamaiedge.net. 1000 IN SOA n0a.akamaiedge.net. hostmaster.akamai.com. 1719824501 1000 1000 1000 1800 ;ADDITIONAL
whatsmydns.net TXT Record Lookup tool lets you query DNS servers and get instant results.
Text Record or TXT record lookups are used to determine the TXT records associated with a domain.
Looking for easier to understand results? Use the Global DNS Checker tool.
TXT records, known as Text records are used to store text data on a domain.
Storing data in TXT records is commonly used to store configuration settings such as SPF or DKIM records to help with reducing email spam, or verification keys to prove ownership of a domain for use in third party services such as analytics or cloud service providers.
An example TXT record may look like the following:
| Record | Type | Value | TTL |
|---|---|---|---|
| example.com | TXT | "v=spf1 include:_spf.google.com ~all" | 3600 |
example.com represents domain of the record.
TXT is the record type.
"v=spf1 include:_spf.google.com ~all" is the value of the record. This example uses a configuration format for the Sender Policy Framework (SPF) used to help prevent spam emails.
3600 is the TTL (time to live) of the record in seconds, this example represents 1 hour. This means that when a record has had updates made to it, then it will take 1 hour to update.
