134.48.90.250
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
- Academic allocation +6
- Long-established allocation (37y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 87 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- reyer.eng.mu.edu
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 600 s
- Reverse DNS last checked
- 2026-11-02 13:55 UTC
Forward DNS records for reyer.eng.mu.edu
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 134.48.90.250 | — | 600s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-11-03 UTC1
Registrable domains (like example.com) with at least one name resolving to this IP — updated daily from issued.live's DNS data.
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.
- reyer.eng.mu.edu — Nov 2, 2026 → present
- a3-82.eece.mu.edu — Nov 1, 2026 → Nov 2, 2026
- reyer.eng.mu.edu — Oct 29, 2026 → Nov 1, 2026
- a3-82.eece.mu.edu — Oct 28, 2026 → Oct 29, 2026
- reyer.eng.mu.edu — Oct 26, 2026 → Oct 28, 2026
- a3-82.eece.mu.edu — Oct 26, 2026 → Oct 26, 2026
- reyer.eng.mu.edu — Oct 25, 2026 → Oct 26, 2026
- a3-82.eece.mu.edu — Oct 24, 2026 → Oct 25, 2026
- reyer.eng.mu.edu — Oct 22, 2026 → Oct 24, 2026
- a3-82.eece.mu.edu — Oct 21, 2026 → Oct 22, 2026
- reyer.eng.mu.edu — Oct 20, 2026 → Oct 21, 2026
- a3-82.eece.mu.edu — Oct 18, 2026 → Oct 20, 2026
- reyer.eng.mu.edu — Oct 16, 2026 → Oct 18, 2026
- a3-82.eece.mu.edu — Oct 14, 2026 → Oct 16, 2026
- reyer.eng.mu.edu — Oct 11, 2026 → Oct 14, 2026
- a3-82.eece.mu.edu — Oct 9, 2026 → Oct 11, 2026
- reyer.eng.mu.edu — Oct 5, 2026 → Oct 9, 2026
- a3-82.eece.mu.edu — Oct 5, 2026 → Oct 5, 2026
- reyer.eng.mu.edu — Oct 3, 2026 → Oct 5, 2026
- a3-82.eece.mu.edu — Sep 29, 2026 → Oct 3, 2026
- reyer.eng.mu.edu — Sep 28, 2026 → Sep 29, 2026
- a3-82.eece.mu.edu — Sep 27, 2026 → Sep 28, 2026
- reyer.eng.mu.edu — Sep 25, 2026 → Sep 27, 2026
- a3-82.eece.mu.edu — Aug 25, 2026 → Sep 25, 2026
- reyer.eng.mu.edu — Aug 19, 2026 → Aug 25, 2026
- a3-82.eece.mu.edu — Aug 16, 2026 → Aug 19, 2026
- reyer.eng.mu.edu — Jun 12, 2026 → Aug 16, 2026
Network Allocation for 134.48.90.250
- CIDR range
- 134.48.80.0/20
- IP range (int)
- 2,251,313,152 — 2,251,317,247
- Prefix length
- /20
- Organization
- Marquette University
- ASN
- AS1736
- ASN name
- Marquette University
- Location
- Brookfield, Wisconsin, United States
- Coordinates
- 43.065600, -88.145000
- Accuracy radius
- 10 km
- Postal code
- 53045
- Regional Internet Registry
- ARIN
- Allocated
- 1989-04-26
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-11-02 08:47:09
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 134.48.90.250?
134.48.90.250 is allocated to Marquette University (AS1736), registered in Brookfield, United States.
Where is 134.48.90.250 located?
The geolocation for 134.48.90.250 maps to Brookfield, 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 134.48.90.250 on?
134.48.90.250 belongs to the 134.48.80.0/20 network block announced by AS1736. This range contains 4,096 addresses.
Does 134.48.90.250 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.
