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
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Established allocation (11y) +3
- Trust score 78 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- raums.net
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-09-27 16:29 UTC
Forward DNS records for raums.net
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 158.69.13.241 | — | 600s |
| A | 80.255.11.145 | — | 600s |
| MX | raums.net | 10 | — |
| NS | ns15.domaincontrol.com | — | — |
| NS | ns16.domaincontrol.com | — | — |
| TXT | v=DMARC1; p=reject; pct=100; rua=mailto:report@raums.net; ruf=mailto:report@raums.net | — | — |
| TXT | v=spf1 ip4:130.51.100.32/30 ip4:148.135.9.216/29 ip4:2.58.197.80 ip4:2.58.197.104/30 ip4:2.58.197.109 ip4:5.254.85.52/30 ip4:5.254.85.64/27 ip4:15.235.134.192/29 ip4:23.94.105.177 ip4:23.94.105.179 ip4:23.94.105.182 ip4:23.94.105.184 ip4:31.57.251.34 ip4:31.57.251.38 ip4:31.57.251.42/31 ip4:31.57.251.88 ip4:45.141.116.125 ip4:50.3.105.242 ip4:50.3.105.244/30 ip4:51.79.43.194 ip4:66.70.215.40/30 ip4:66.85.185.124 ip4:103.126.162.248/29 ip4:103.252.46.158/31 ip4:103.252.46.160/28 ip4:141.11.103.3 ip4:141.11.1 | — | — |
| TXT | v=spf1 ip4:15.235.134.192/29 ip4:23.94.105.177 ip4:23.94.105.179 ip4:23.94.105.182 ip4:23.94.105.184 ip4:50.2.184.80/29 ip4:50.2.184.86 ip4:50.3.105.242 ip4:50.3.105.244/30 ip4:51.79.43.194 ip4:66.70.215.40/30 ip4:66.85.185.124 ip4:79.141.170.49 ip4:79.141.171.203 ip4:85.206.174.56/29 ip4:91.193.17.132 ip4:103.126.162.248/29 ip4:103.252.46.158/31 ip4:103.252.46.160/28 ip4:130.51.100.32/30 ip4:141.11.103.3 ip4:141.11.103.4/30 ip4:141.11.103.8/31 ip4:162.250.232.110 ip4:162.250.232.114 ip4:162.250.232.147 i | — | — |
| TXT | v=spf1 ip4:15.235.134.192/29 ip4:23.94.105.177 ip4:23.94.105.179 ip4:23.94.105.182 ip4:23.94.105.184 ip4:50.2.184.80/29 ip4:50.2.184.86 ip4:50.3.105.242 ip4:50.3.105.244/30 ip4:51.79.43.194 ip4:66.70.215.40/30 ip4:66.85.185.124 ip4:85.206.174.56/29 ip4:103.126.162.248/29 ip4:103.252.46.158/31 ip4:103.252.46.160/28 ip4:130.51.100.32/30 ip4:141.11.103.3 ip4:141.11.103.4/30 ip4:141.11.103.8/31 ip4:162.250.232.110 ip4:162.250.232.114 ip4:162.250.232.147 ip4:162.250.232.152/30 ip4:184.164.142.54 ip4:184.164.14 | — | — |
| TXT | v=spf1 ip4:158.69.13.241 include:_spf.google.com -all | — | — |
| TXT | v=spf1 ip4:194.15.112.44 ip4:194.15.112.238 ip4:194.15.113.132 ip4:194.15.113.165 ip4:194.15.113.225 ip4:66.85.185.124 ip4:184.164.142.54 ip4:184.164.142.62 ip4:184.164.146.125 ip4:5.254.85.52/30 ip4:5.254.85.64/27 ip4:31.57.251.34 ip4:31.57.251.38 ip4:31.57.251.42/31 ip4:31.57.251.88 ip4:15.235.134.192/29 ip4:23.94.105.177 ip4:23.94.105.179 ip4:23.94.105.182 ip4:23.94.105.184 ip4:50.2.184.80/29 ip4:50.2.184.86 ip4:50.3.105.242 ip4:50.3.105.244/30 ip4:51.79.43.194 ip4:66.70.215.40/30 ip4:103.126.162.248/2 | — | — |
| TXT | v=spf1 ip4:2.58.197.80 ip4:2.58.197.104/30 ip4:2.58.197.109 ip4:5.254.85.52/30 ip4:5.254.85.64/27 ip4:15.235.134.192/29 ip4:23.94.105.177 ip4:23.94.105.179 ip4:23.94.105.182 ip4:23.94.105.184 ip4:31.57.251.34 ip4:31.57.251.38 ip4:31.57.251.42/31 ip4:31.57.251.88 ip4:45.141.116.125 ip4:50.3.105.242 ip4:50.3.105.244/30 ip4:51.79.43.194 ip4:66.70.215.40/30 ip4:66.85.185.124 ip4:103.126.162.248/29 ip4:103.252.46.158/31 ip4:103.252.46.160/28 ip4:130.51.100.32/30 ip4:141.11.103.3 ip4:141.11.103.4/30 ip4:141.11.10 | — | — |
| TXT | v=spf1 ip4:50.3.105.242 ip4:50.3.105.244/30 ip4:51.79.43.194 ip4:66.70.215.40/30 ip4:66.85.185.124 ip4:103.126.162.248/29 ip4:162.250.232.110 ip4:162.250.232.114 ip4:162.250.232.147 ip4:162.250.232.152/30 ip4:184.164.142.54 ip4:184.164.142.62 ip4:184.164.146.125 ip4:193.19.178.24/29 ip4:194.102.33.89 ip4:194.102.33.196/30 ip4:202.155.151.0/26 ip4:80.255.11.145 include:_spf.google.com -all | — | — |
| TXT | v=spf1 ip4:50.3.105.242 ip4:50.3.105.244/30 ip4:51.79.43.194 ip4:66.70.215.40/30 ip4:66.85.185.124 ip4:103.126.162.248/29 ip4:184.164.142.54 ip4:184.164.142.62 ip4:184.164.146.125 ip4:193.19.178.24/29 ip4:80.255.11.145 include:_spf.google.com -all | — | — |
| TXT | v=spf1 ip4:80.255.11.145 include:_spf.google.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.
Reverse-DNS changes between Jun 19, 2026 and Aug 18, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- raums.net — since at least Aug 18, 2026 → present
- ruqyadirectory.com stable — Jun 19, 2026 → Aug 18, 2026
Network Allocation for 158.69.13.241
- CIDR range
- 158.69.12.0/23
- IP range (int)
- 2,655,325,184 — 2,655,325,695
- Prefix length
- /23
- Organization
- OVH SAS
- ASN
- AS16276
- ASN name
- OVH SAS
- Location
- Montreal, Quebec, Canada
- Coordinates
- 45.507500, -73.588700
- Accuracy radius
- 20 km
- Postal code
- H3H
- Regional Internet Registry
- ARIN
- Allocated
- 2015-06-15
- Data source(s)
- maxmind_city, maxmind_country, ipinfo_lite, maxmind_asn
- Last updated
- 2026-09-27 05:24:32
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 158.69.13.241?
158.69.13.241 is allocated to OVH SAS (AS16276), registered in Montreal, Canada.
Where is 158.69.13.241 located?
The geolocation for 158.69.13.241 maps to Montreal, Canada 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 158.69.13.241 on?
158.69.13.241 belongs to the 158.69.12.0/23 network block announced by AS16276. This range contains 512 addresses.
Does 158.69.13.241 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.
