104.161.23.180
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
- Forward-confirmed reverse DNS (FCrDNS) +10
- Not on any threat blocklist +5
- Established allocation (12y) +3
- Trust score 83 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- terc.uc.edu
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-07-18 15:41 UTC
- Forward DNS last checked
- 2026-07-18 15:41 UTC
Forward DNS records for terc.uc.edu
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 104.161.23.180 | — | 172800s |
| A | 15.204.132.128 | — | 172800s |
| A | 163.172.87.67 | — | 172800s |
| A | 172.104.151.163 | — | 172800s |
| A | 198.71.61.168 | — | 172800s |
| A | 198.71.61.88 | — | 172800s |
| A | 212.83.140.213 | — | 172800s |
| A | 212.83.140.216 | — | 172800s |
| A | 212.83.140.238 | — | 172800s |
| A | 51.195.111.216 | — | 172800s |
| A | 51.195.111.217 | — | 172800s |
| A | 51.195.111.218 | — | 172800s |
| A | 51.195.111.219 | — | 172800s |
| A | 51.195.111.220 | — | 172800s |
| A | 51.81.146.30 | — | 172800s |
| A | 51.81.146.32 | — | 172800s |
| A | 51.81.148.228 | — | 172800s |
| A | 51.81.148.229 | — | 172800s |
| A | 51.81.148.233 | — | 172800s |
| A | 51.81.148.234 | — | 172800s |
| A | 51.81.202.103 | — | 172800s |
| A | 51.81.73.108 | — | 172800s |
| A | 57.129.123.180 | — | 172800s |
| A | 74.208.178.108 | — | 172800s |
| A | 74.208.30.38 | — | 172800s |
| A | 74.208.95.177 | — | 172800s |
| A | 82.165.162.92 | — | 172800s |
| A | 82.165.21.85 | — | 172800s |
| A | 82.165.21.88 | — | 172800s |
| A | 93.90.207.251 | — | 172800s |
| AAAA | 2600:3c00::2000:ecff:fe5a:3219 | — | 172800s |
| AAAA | 2600:3c01::2000:b8ff:fed3:c98c | — | 172800s |
| AAAA | 2600:3c02::2000:73ff:fe9c:81cb | — | 172800s |
| AAAA | 2600:3c03::2000:5bff:fecd:16f3 | — | 172800s |
| AAAA | 2600:3c04::2000:e9ff:fe29:6ca1 | — | 172800s |
| AAAA | 2a01:7e01::2000:75ff:fea7:3466 | — | 172800s |
| TXT | v=spf1 include:glorywinner.com include:notserd.live include:marketerpoolish.us.org include:basenewss.com include:kqcsport.com include:vejday.com include:news-latimes.com include:www-test-lacoste.com include:speedsmalse.info include:libomail.com -all | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
- terc.uc.edu — Jul 8, 2026 → present
- join.liujo.com stable — Jun 11, 2026 → Jul 8, 2026
Network Allocation for 104.161.23.180
- CIDR range
- 104.161.22.0/23
- IP range (int)
- 1,755,387,392 — 1,755,387,903
- Prefix length
- /23
- Organization
- Input Output Flood LLC
- ASN
- AS53755
- ASN name
- Input Output Flood LLC
- Location
- United States
- Coordinates
- 37.751000, -97.822000
- Accuracy radius
- 1000 km
- Regional Internet Registry
- ARIN
- Allocated
- 2014-07-28
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-07-09 12:20:26
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 104.161.23.180?
104.161.23.180 is allocated to Input Output Flood LLC (AS53755), registered in United States.
Where is 104.161.23.180 located?
The geolocation for 104.161.23.180 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 104.161.23.180 on?
104.161.23.180 belongs to the 104.161.22.0/23 network block announced by AS53755. This range contains 512 addresses.
Does 104.161.23.180 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.
