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 (38y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- evo.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-09-23 07:46 UTC
- Forward DNS last checked
- 2026-09-23 07:46 UTC
Forward DNS records for evo.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 104.18.28.77 | — | 300s |
| A | 104.18.29.77 | — | 300s |
| AAAA | 2606:4700::6812:1c4d | — | 172800s |
| AAAA | 2606:4700::6812:1d4d | — | 172800s |
| MX | evo-com.mail.protection.outlook.com | 0 | — |
| NS | anuj.ns.cloudflare.com | — | — |
| NS | aria.ns.cloudflare.com | — | — |
| TXT | 5mi69gdltloeu0u83oefe8np76 | — | — |
| TXT | 6v96qhc2aantqervh7983hvq8r | — | — |
| TXT | anthropic-domain-verification-2swdt9=MGB5osN2bbE5axbJun9qrjdzp | — | — |
| TXT | apple-domain-verification=TnevgwBI6m8knsq2 | — | — |
| TXT | atlassian-domain-verification=yGEmEsWGcMDXva9EOzw/RyejzE5M0FLw8RwKwRFYYXJxwyyRU4aHOi8qsW45WeJe | — | — |
| TXT | atlassian-sending-domain-verification=b49ec3ee-b793-4f5f-900d-202bf624caf0 | — | — |
| TXT | facebook-domain-verification=uyrt7d4ry1xe0tro1oao4sl2qqnas5 | — | — |
| TXT | google-site-verification=AHbZVHgQYpNPBE7Al8-h5xOpohw0UmjCp_W5iEB6MA0 | — | — |
| TXT | google-site-verification=CTlyBPnmVaQM138eF896DMnDiLvfWS15K3pJBl7cE0Y | — | — |
| TXT | google-site-verification=DQ8y-_S5eLcX2RqPvibGv4Hq_i2N2rJplApeEIvTqyI | — | — |
| TXT | google-site-verification=k3kdFY2YZG2B6eD96mrpLOnHY6eZSUUrR3ALBsPtzcw | — | — |
| TXT | ib04mui59qqhg5o2aiidnvk6f | — | — |
| TXT | klaviyo-site-verification=XsNjgV | — | — |
| TXT | openai-domain-verification=dv-TRG42MrxsiV8neKgnZiio3rk | — | — |
| TXT | samsung-domain-verification=9b53a42b-a438-4763-967d-62deda339e75 | — | — |
| TXT | v=DMARC1; p=reject; rua=mailto:0397f319da6e4903b7b4894c5294a2e1@dmarc-reports.cloudflare.net; | — | — |
| TXT | v=spf1 ip4:50.235.1.250 ip4:50.235.1.186 ip4:62.116.174.47 ip6:2001:4178:6:1066:62:116:174:47 include:spf.protection.outlook.com include:sent-via.netsuite.com include:_spf.mailgun.org -all | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 130.49.181.69
- CIDR range
- 130.49.181.0/24
- IP range (int)
- 2,184,295,680 — 2,184,295,935
- Prefix length
- /24
- Organization
- Time-host Ltd
- ASN
- AS212913
- ASN name
- Time-host Ltd
- Location
- Russia
- Coordinates
- 55.738600, 37.606800
- Accuracy radius
- 1000 km
- Regional Internet Registry
- RIPE
- Allocated
- 1988-05-18
- Data source(s)
- maxmind_asn, ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-08-09 13:24:05
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 |
See the full history for 130.49.176.0/20.
Frequently Asked Questions
Who owns 130.49.181.69?
130.49.181.69 is allocated to Time-host Ltd (AS212913), registered in Russia.
Where is 130.49.181.69 located?
The geolocation for 130.49.181.69 maps to Russia 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 130.49.181.69 on?
130.49.181.69 belongs to the 130.49.181.0/24 network block announced by AS212913. This range contains 256 addresses.
Does 130.49.181.69 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.
