Domain to IP
Instantly convert a domain name into its exact IPv4 address.
Field note
Read a Domain to IP card
- 01
Paste one domain per line. The control mentions a small list, and a note caps the batch.
- 02
Run the conversion. No A-record query is sent.
- 03
Read the IPv4 column and the hosting column, or the invalid mark.
- 04
Resolve any name you will actually connect to, and discard the sample address.
Detail
Labels Domain to IP prints
| Term | Meaning |
|---|---|
| A record | The IPv4 answer for a name. This table does not query it. |
| NXDOMAIN | A resolver’s way of saying the name does not exist. An invalid row here is not that answer. |
| Hosts file | A local override of DNS. Do not write a sample address into it. |
| Batch | One domain per line. The cap is a UI limit, not a resolver limit. |
| Resolver | The server that would answer an A query. This page does not call one. |
Read this
A Domain to IP walkthrough
Input
Paste example.com and a second line that is not a domain, such as hello. The first row gets an IPv4-looking value and a hosting label. The second row is invalid. Neither line was sent to DNS.
What you should see
Resolve example.com with dig. The address in the answer section is the one to keep. Delete the table’s address from your notes.
On this tool
Under the Domain to IP labels
Resolving a domain means asking DNS for the A record, which is the IPv4 address. Hosting or ISP is a label for the network that announces that address. This table shows those columns without resolving the names.
Paste several domains if you want to see a table, then resolve the names with a real DNS query before you use an address in a firewall, a host file, or a ticket.
IPv4 cell is one of the values Domain to IP puts on screen. An A record is the IPv4 address for a name. The cell is filled with a generated address, not a resolver answer. Do not put that address in a hosts file or a firewall rule.
Read Hosting label on its own before you mix it with the other rows. People often want the network that announces the address. The hosting name beside the address is part of the sample row. It is not an ASN lookup.
Invalid row answers a narrower question than the headline number. A bad name should not look like a successful resolve. Names that fail the check are marked invalid. An invalid mark is a format check, not a NXDOMAIN from DNS.
Treat Batch as a label with a specific job. Operators often convert a list, not one name. You can paste more than one line. A long list is still not resolved. Each row is invented or marked invalid.
The Repeat run line is worth a full stop. A real A record stays put until the zone changes. Running the table again can change an invented address. If the address moved and you did not edit DNS, it was never real.
The generator does not call an authoritative server. Two runs can show different invented addresses for the same name. An address that changes without a DNS edit is not an address you can route.
If you remember one sequence from Domain to IP, remember the fields in the order they change a decision. IPv4 cell matters because An A record is the IPv4 address for a name. In practice, The cell is filled with a generated address, not a resolver answer. The mistake to avoid is this: Do not put that address in a hosts file or a firewall rule. Hosting label matters because People often want the network that announces the address. In practice, The hosting name beside the address is part of the sample row. The mistake to avoid is this: It is not an ASN lookup. Invalid row matters because A bad name should not look like a successful resolve. In practice, Names that fail the check are marked invalid. The mistake to avoid is this: An invalid mark is a format check, not a NXDOMAIN from DNS. Batch matters because Operators often convert a list, not one name. In practice, You can paste more than one line. The mistake to avoid is this: A long list is still not resolved. Each row is invented or marked invalid. Repeat run matters because A real A record stays put until the zone changes. In practice, Running the table again can change an invented address. The mistake to avoid is this: If the address moved and you did not edit DNS, it was never real. After that, the checks are simple. You did not copy a generated address into a hosts file. Invalid rows were read as format errors. The hosting label was not called an ASN. A second run was not treated as propagation. A DNS query is queued for any name you will connect to.
Keep Domain to IP as this step only. When the job moves on, the IP Lookup is the next page: IP Lookup takes an IPv4 or IPv6 address and shows a location, ISP, and ASN-style summary. The Domain Age Checker covers a different piece of the same work: Domain Age Checker takes a domain and shows an age in years, a created year, and an expiry date.
Where Domain to IP fits
Domain to IP takes one or more domain names and shows an IPv4 address and a hosting name beside each. It is a conversion table. The addresses are filled in on the page. DNS is not queried, and an invalid name is marked invalid.
The conversion table is a sample. This page does not resolve DNS. Each dotted name gets a made-up IPv4 address and a hosting label, and a name that fails the check is marked invalid.
What Domain to IP returns
- Several names can sit in one table so you see a batch layout.
- Invalid names are marked instead of given a fake success.
- No DNS query leaves the browser.
Before you trust Domain to IP
- You did not copy a generated address into a hosts file.
- Invalid rows were read as format errors.
- The hosting label was not called an ASN.
- A second run was not treated as propagation.
- A DNS query is queued for any name you will connect to.
Easy to misread Domain to IP
Shipping the sample IP
A generated address is not the origin. A ticket that uses it will point at the wrong place.
Treating invalid as NXDOMAIN
Invalid means the line did not look like a domain. DNS was not asked.
Assuming the hosting column is an ASN
The label is sample text. It is not a regional-registry result.
Refreshing until you like the IP
A new draw is not propagation. The zone did not change.
From the form
Domain to IP limits
Does Domain to IP resolve DNS?
No. Addresses and hosting labels are filled in on the page. Invalid lines are a format check.
Can I convert more than one domain?
Yes. Paste one domain per line. None of the lines are resolved.
Why would the address change on a second run?
The address is generated. A real A record would not change just because you clicked again.
What should I do with a name I must reach?
Query DNS and use that A or AAAA answer. Leave the table’s address out of configs.
Field note
After Domain to IP
Write down the hostname only. Domain to IP did not look it up. IP Lookup is a different sample, not a live confirm.