45.11.89.133
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
- Multiple-origin (MOAS) routing anomaly −12
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 63 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- yanxiazhang.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 14400 s
- Reverse DNS last checked
- 2026-07-18 21:24 UTC
- Forward DNS last checked
- 2026-07-18 21:24 UTC
Forward DNS records for yanxiazhang.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 193.39.184.235 | — | 447s |
| MX | yanxiazhang.com | 10 | — |
| NS | dns1.registrar-servers.com | — | — |
| NS | dns2.registrar-servers.com | — | — |
| NS | ns1.yanxiazhang.com | — | — |
| NS | ns2.yanxiazhang.com | — | — |
| TXT | v=DMARC1; p=reject; pct=100; rua=mailto:report@yanxiazhang.com; ruf=mailto:report@yanxiazhang.com | — | — |
| TXT | v=spf1 ip4:173.252.193.187 ip4:62.204.35.36 ip4:62.204.35.178 ip4:62.204.35.250 ip4:146.19.49.23 ip4:146.19.49.153 ip4:185.222.31.96/28 ip4:74.82.170.106 ip4:95.179.151.179 ip4:185.92.222.138 ip4:192.34.80.219 ip4:192.34.80.221 ip4:23.106.37.21 ip4:23.106.37.27 ip4:67.23.233.204 ip4:45.32.199.203 ip4:104.238.147.165 -all | — | — |
| TXT | v=spf1 ip4:185.222.31.96/28 ip4:67.23.233.204 ip4:45.32.199.203 ip4:104.238.147.165 -all | — | — |
| TXT | v=spf1 ip4:185.222.31.96/28 ip4:74.82.170.106 ip4:95.179.151.179 ip4:185.92.222.138 ip4:192.34.80.219 ip4:192.34.80.221 ip4:173.252.193.187 ip4:23.106.37.21 ip4:23.106.37.27 ip4:67.23.233.204 ip4:45.32.199.203 ip4:104.238.147.165 -all | — | — |
| TXT | v=spf1 ip4:193.39.184.235 include:_spf.google.com -all | — | — |
| TXT | v=spf1 ip4:67.23.233.204 ip4:173.252.193.187 ip4:185.92.222.138 ip4:185.187.155.109 ip4:62.204.35.36 ip4:62.204.35.178 ip4:62.204.35.250 ip4:146.19.49.23 ip4:146.19.49.153 ip4:185.222.31.96/28 ip4:74.82.170.106 ip4:95.179.151.179 ip4:192.34.80.219 ip4:192.34.80.221 ip4:23.106.37.21 ip4:23.106.37.27 ip4:45.32.199.203 ip4:104.238.147.165 -all | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 45.11.89.133
- CIDR range
- 45.11.89.0/24
- IP range (int)
- 755,718,400 — 755,718,655
- Prefix length
- /24
- Organization
- Heymman Servers Corporation
- ASN
- AS152900
- ASN name
- Onidel Pty Ltd
- Location
- Kansas City, Missouri, United States
- Coordinates
- 39.148400, -94.568600
- Accuracy radius
- 20 km
- Postal code
- 64116
- Regional Internet Registry
- RIPE
- Allocated
- 2019-04-26
- Data source(s)
- ipinfo_lite, maxmind_city, maxmind_country, maxmind_asn
- Last updated
- 2026-07-18 14:05:12
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured weekly from regional internet registry (RIR) delegation files for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | RIR Transfer | arin | ripe |
| 2026-05-10 | Country Change | US | CA |
See the full history for 45.11.88.0/22.
Frequently Asked Questions
Who owns 45.11.89.133?
45.11.89.133 is allocated to Heymman Servers Corporation (AS152900), registered in Kansas City, United States.
Where is 45.11.89.133 located?
The geolocation for 45.11.89.133 maps to Kansas City, 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 45.11.89.133 on?
45.11.89.133 belongs to the 45.11.89.0/24 network block announced by AS152900. This range contains 256 addresses.
Does 45.11.89.133 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.
