Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Long-established allocation (23y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Enterprise allocation +4
- Trust score 85 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- om-in-f99.1e100.net
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-10-12 08:18 UTC
Forward DNS records for om-in-f99.1e100.net
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 64.233.179.99 | — | 172800s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-10-11 UTC0
issued.live saw no domain resolving to this IP in its latest weekly snapshot.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
Reverse-DNS changes between Oct 11, 2026 and Oct 12, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- om-in-f99.1e100.net — since at least Oct 12, 2026 → present
- yucbfab-in-f99.1e100.net — Oct 11, 2026 → Oct 12, 2026
- om-in-f99.1e100.net — Oct 10, 2026 → Oct 11, 2026
- yucbfab-in-f99.1e100.net — Oct 6, 2026 → Oct 10, 2026
- om-in-f99.1e100.net — Oct 5, 2026 → Oct 6, 2026
- yucbfab-in-f99.1e100.net — Oct 4, 2026 → Oct 5, 2026
- om-in-f99.1e100.net — Oct 3, 2026 → Oct 4, 2026
- yucbfab-in-f99.1e100.net — Oct 2, 2026 → Oct 3, 2026
- om-in-f99.1e100.net — Sep 30, 2026 → Oct 2, 2026
- yucbfab-in-f99.1e100.net — Sep 28, 2026 → Sep 30, 2026
- om-in-f99.1e100.net — Sep 27, 2026 → Sep 28, 2026
- yucbfab-in-f99.1e100.net — Sep 26, 2026 → Sep 27, 2026
- om-in-f99.1e100.net — Sep 25, 2026 → Sep 26, 2026
- yucbfab-in-f99.1e100.net — Aug 25, 2026 → Sep 25, 2026
- om-in-f99.1e100.net — Aug 24, 2026 → Aug 25, 2026
- yucbfab-in-f99.1e100.net — Aug 18, 2026 → Aug 24, 2026
- om-in-f99.1e100.net — Aug 17, 2026 → Aug 18, 2026
- yucbfab-in-f99.1e100.net — Jun 29, 2026 → Aug 17, 2026
- om-in-f99.1e100.net — Jun 21, 2026 → Jun 29, 2026
- yucbfab-in-f99.1e100.net — Jun 12, 2026 → Jun 21, 2026
- om-in-f99.1e100.net — Jun 11, 2026 → Jun 12, 2026
Network Allocation for 64.233.179.99
- CIDR range
- 64.233.179.0/24
- IP range (int)
- 1,089,057,536 — 1,089,057,791
- Prefix length
- /24
- Organization
- Google, LLC
- ASN
- AS15169
- ASN name
- Google LLC
- Location
- United States
- Coordinates
- 37.751000, -97.822000
- Accuracy radius
- 1000 km
- Regional Internet Registry
- ARIN
- Allocated
- 2003-08-18
- Data source(s)
- ipinfo_lite, maxmind_city, maxmind_country, maxmind_asn
- Last updated
- 2026-10-12 02:32:24
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 64.233.179.99?
64.233.179.99 is allocated to Google, LLC (AS15169), registered in United States.
Where is 64.233.179.99 located?
The geolocation for 64.233.179.99 maps to United States based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 64.233.179.99 on?
64.233.179.99 belongs to the 64.233.179.0/24 network block announced by AS15169. This range contains 256 addresses.
Does 64.233.179.99 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
