DNS.fish

$ Quick DNS Record Lookup Tool_

> DNS records for editapp.io

Name Type Data TTL
www.editapp.ioA 162.19.74.185 3600
admin.editapp.ioA 162.19.74.185 3600
app.editapp.ioA 146.59.155.165 3600
api.editapp.ioA 146.59.155.165 3600
editapp.ioA 162.19.74.185 3600
editapp.ioAAAA 2001:41d0:304:200::1e69 3600
ftp.editapp.ioCNAME editapp.io 3600
editapp.ioMX 10 alt4.aspmx.l.google.com. 3600
editapp.ioMX 10 alt3.aspmx.l.google.com. 3600
editapp.ioMX 5 alt2.aspmx.l.google.com. 3600
editapp.ioMX 5 alt1.aspmx.l.google.com. 3600
editapp.ioMX 1 aspmx.l.google.com. 3600
editapp.ioNS dns106.ovh.net 3600
editapp.ioNS ns106.ovh.net 3600
editapp.ioSOA dns106.ovh.net. tech.ovh.net. 2024112400 86400 3600 3600000 60 3600
editapp.ioTXT "stripe-verification=929b0f3b91fbef9d88d0f00723c3ee2d65096601e29a2c91019846f0a023dea7" 3600
editapp.ioTXT "google-site-verification=xTL1sXhPJRlPBU4OL-sQc1oguUHP9awCJwq4jak2Vx8" 3600
editapp.ioTXT "sendinblue-code:e736bcb69f4a9bcc2dd5f7451dfc4844" 3600
editapp.ioTXT "v=spf1 include:_spf.google.com ~all" 3600

> Export DNS Records for editapp.io

Need PDF format? Easily convert TXT to PDF with PDF Dance .

> About DNS.fish

DNS.fish: Powerful tool for quick DNS record lookups. The alternative to nslookup.io. Built for devs, sysadmins, and curious minds. Simple curl commands. Fast results. No BS.

> Domain DNS Lookup API Usage

$ Get all DNS records:

curl dns.fish/editapp.io

$ Get specific type records:

curl dns.fish/editapp.io/TYPE

Replace DOMAIN with target domain, TYPE with DNS record type (A, AAAA, MX, etc.).

> Features

  • • Fast and live DNS record lookups
  • • All common DNS record types supported
  • • Zero install, supports CLI(API) usage
  • • Blazing fast response times
  • • Clean, parsable output
  • • Export & Download DNS records

> FAQ

Q: What is a DNS record?

A: A DNS record is a database entry in the Domain Name System that maps a domain name to specific information, such as IP addresses or other data related to the domain.

Q: Why is it important to check DNS records?

A: Checking DNS records is crucial for several reasons:

  • Troubleshooting: Helps identify and resolve website accessibility issues
  • Security: Verifies proper configuration to prevent DNS-based attacks
  • Email delivery: Ensures correct MX records for smooth email flow
  • Performance: Confirms optimal DNS settings for fast website loading
  • Migrations: Validates DNS changes during website or server migrations
  • Compliance: Assists in maintaining required security standards

Regular DNS record checks help maintain a healthy, secure, and efficient online presence.

Q: What are the most common types of DNS records?

A: The most common types of DNS records include:

  • A (Address) record: Maps a domain to an IPv4 address
  • AAAA record: Maps a domain to an IPv6 address
  • CNAME (Canonical Name) record: Aliases one domain to another
  • MX (Mail Exchanger) record: Specifies mail servers for the domain
  • TXT (Text) record: Stores text-based information, often used for SPF, DKIM, etc.
  • NS (Name Server) record: Specifies authoritative name servers for the domain

Q: What is the difference between A and AAAA records?

A: A records map a domain to an IPv4 address (e.g., 192.0.2.1), while AAAA records map a domain to an IPv6 address (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334).

Q: What is a CNAME record used for?

A: A CNAME record is used to create an alias for a domain. It points one domain name to another, allowing multiple domains to resolve to the same IP address without duplicate A or AAAA records.

Q: How do MX records work?

A: MX records specify the mail servers responsible for handling email for a domain. They include a priority value to determine the order in which mail servers should be tried.

Q: What is a TTL in DNS records?

A: TTL stands for Time To Live. It specifies how long (in seconds) a DNS record should be cached by resolving name servers before requesting a fresh copy from the authoritative name server.

> Recent DNS Lookups

Note: Only domains with more than 3 DNS records are displayed here. CURL requests are not shown.