We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Get the latest and fastest GitHub IP addresses in real-time to fix slow access caused by DNS spoofing.
Resolve common GitHub domains to their current IPv4 addresses and generate a Hosts suggestion that is easy to inspect and copy.
Before you use these entries
Each domain uses the first IPv4 address returned by public DNS. TTL is shown to indicate how quickly an answer may change.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This lookup displays the IPv4 result seen by the service's DNS resolver for seven preset GitHub-related hostnames: github.com, api.github.com, raw.githubusercontent.com, codeload.github.com, objects.githubusercontent.com, avatars.githubusercontent.com, and github.githubassets.com. For each hostname, the table shows whether resolution succeeded, one returned IPv4 address when available, and the record's TTL in seconds. It also shows when the snapshot was generated and provides copyable hosts-format lines for successful results.
DNS (Domain Name System) maps names such as github.com to network addresses. A hosts file is a local text file that can provide a name-to-address mapping on a device; its usual line order is IP address, then hostname. The output is a convenient snapshot and draft mapping, not an official GitHub address list, a complete domain inventory, or a test of your computer's DNS, route, latency, or connection quality. GitHub notes that its IP ranges can change and that published IP information is not exhaustive. For managed networks, consult GitHub's restricted-network guidance and your administrator.
TTL means time to live: the number of seconds a DNS answer may be cached by a resolver. It helps interpret how soon an answer may be refreshed; it does not promise the IP will keep working for that period or afterwards. See RFC 1035 for DNS background and the hosts file format reference.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
The page loads a fresh snapshot when opened. Select Refresh DNS to request it again. Check the displayed generation time so you know which snapshot you are reviewing.
Each row corresponds to one of the seven preset names. A resolved row has an IPv4 address; a failed row has no usable address. Compare TTL values as DNS cache information, not as an uptime countdown or an indication of speed.
Copy a single line or the successful entries as a block. A hosts entry follows the form 203.0.113.10 github.com (the address here is only an illustrative documentation-range example). Verify every address-name pair and check that the mapping suits your device and purpose before saving anything locally.
Use cases
See how the tool fits into real work and everyday tasks.
A developer investigating a hostname that fails in one environment can compare this snapshot with a lookup from the affected computer or network. A difference is a clue to investigate DNS configuration; the snapshot does not establish which route or address will work best for that user.
An administrator or technically experienced user can inspect the generated lines as a starting point for review. Confirm whether a local override is appropriate, follow organizational change procedures, and preserve the previous file so the change can be reversed.
Q&A
Find concise answers to common questions and confusing cases.
No. It shows one IPv4 answer from the lookup environment. It does not measure your local route, latency, throughput, or reachability, and it cannot rank addresses for your connection.
Your device and this lookup may use different resolvers and network paths, so their DNS answers can differ. Compare results from the affected device and ask your network administrator to investigate if the difference affects managed access.
Do not treat this small set of current answers as a firewall allowlist. GitHub publishes separate IP information, says addresses may change, and warns that its published ranges and service-domain lists are not comprehensive. Use current official network guidance and your organization's policy.
The lookup did not return a usable IPv4 result for that hostname in this request. It does not prove the domain is offline or unavailable from your network. Refresh later and check from the environment where the problem occurs.
Notes
Review scope, result limitations, and important precautions before use.
This snapshot is limited to seven preset hostnames and one IPv4 answer per successful lookup. Results reflect the resolver environment and retrieval time, may change, and do not establish a permanent mapping, complete GitHub coverage, or a fix for connectivity problems. Adding a hosts entry overrides normal name lookup for that hostname and can make access worse when the address changes. Do not use static entries to bypass workplace, school, or service access controls. If you choose to edit a system hosts file, follow the device owner's policy, keep a backup, and know how to remove the entries. For managed access issues, work with the network administrator.
Related
Discover related tools, collections, and available API capabilities.