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 (16y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- vexalorn.info
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 604800 s
- Reverse DNS last checked
- 2026-07-08 22:32 UTC
- Forward DNS last checked
- 2026-07-08 22:32 UTC
Forward DNS records for vexalorn.info
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 193.34.212.136 | — | 172800s |
| A | 43.254.30.205 | — | 172800s |
| MX | contact.vexalorn.info | 0 | — |
| MX | mx.vexalorn.info | 0 | — |
| NS | dns1.p17.nsone.net | — | — |
| NS | dns1.p18.nsone.net | — | — |
| NS | dns2.p02.nsone.net | — | — |
| NS | dns2.p15.nsone.net | — | — |
| NS | dns3.p08.nsone.net | — | — |
| NS | dns3.p16.nsone.net | — | — |
| NS | dns4.p03.nsone.net | — | — |
| NS | dns4.p16.nsone.net | — | — |
| TXT | v=DMARC1; p=none; rua=mailto:dmarc@vexalorn.info; ruf=mailto:dmarc@vexalorn.info; sp=none; aspf=s; adkim=r; pct=100; rf=afrf; ri=86400; | — | — |
| TXT | v=spf1 a:dns.vexalorn.info ~all | — | — |
| TXT | v=spf1 ip4:193.34.212.136 ~all | — | — |
| TXT | v=spf1 ip4:5.196.163.162 ip4:5.196.163.163 ip4:5.196.163.164 ip4:5.196.163.165 ip4:5.196.163.166 ip4:5.196.163.167 ip4:5.196.163.168 ip4:5.196.163.169 ip4:5.196.163.170 ip4:5.196.163.171 ip4:5.196.163.172 ip4:5.196.163.173 ip4:5.196.163.174 ip4:43.254.30.195 ip4:43.254.30.201 ip4:43.254.30.202 ip4:43.254.30.203 ip4:43.254.30.205 ip4:43.254.30.206 ip4:81.17.129.162 ip4:81.17.129.163 ip4:81.17.129.164 ip4:81.17.129.165 ip4:81.17.129.166 ip4:81.17.129.167 ip4:81.17.129.168 ip4:81.17.129.169 ip4:81.17.129.170 | — | — |
| TXT | v=spf1 ip4:51.161.51.162 ip4:51.161.51.163 ip4:51.161.51.164 ip4:51.161.51.165 ip4:51.161.51.166 ip4:51.161.51.167 ip4:51.161.51.168 ip4:51.161.51.169 ip4:51.161.51.170 ip4:51.161.51.171 ip4:51.161.51.172 ip4:51.161.51.173 ip4:51.161.51.174 ip4:51.161.51.175 ip4:51.161.51.176 ip4:51.161.51.177 ip4:51.161.51.178 ip4:51.161.51.179 ip4:51.161.51.180 ip4:51.161.51.181 ip4:51.161.51.182 ip4:51.161.51.183 ip4:51.161.51.184 ip4:51.161.51.185 ip4:51.161.51.186 ip4:51.161.51.187 ip4:51.161.51.188 ip4:51.161.51.189 | — | — |
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-04 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.
- no PTR — Jul 8, 2026 → present
- vexalorn.info stable — Jun 13, 2026 → Jul 8, 2026
Network Allocation for 193.34.212.136
- CIDR range
- 193.34.212.0/23
- IP range (int)
- 3,240,285,184 — 3,240,285,695
- Prefix length
- /23
- Organization
- MEVSPACE sp. z o.o.
- ASN
- AS201814
- ASN name
- MEVSPACE sp. z o.o.
- Location
- Poland
- Coordinates
- 52.239400, 21.036200
- Accuracy radius
- 200 km
- Regional Internet Registry
- RIPE
- Allocated
- 2010-04-06
- Data source(s)
- maxmind_asn, ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-10-04 08:49: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 193.34.212.136?
193.34.212.136 is allocated to MEVSPACE sp. z o.o. (AS201814), registered in Poland.
Where is 193.34.212.136 located?
The geolocation for 193.34.212.136 maps to Poland 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 193.34.212.136 on?
193.34.212.136 belongs to the 193.34.212.0/23 network block announced by AS201814. This range contains 512 addresses.
Does 193.34.212.136 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.
