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
- Forward-confirmed reverse DNS (FCrDNS) +10
- Long-established allocation (22y) +6
- Not on any threat blocklist +5
- Isp allocation +5
- Trust score 91 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- tilefish.co.uk
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-10-03 23:47 UTC
- Forward DNS last checked
- 2026-10-03 23:47 UTC
Forward DNS records for tilefish.co.uk
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 185.121.133.233 | — | 172800s |
| A | 31.56.32.104 | — | 300s |
| A | 45.128.118.11 | — | 172800s |
| A | 84.234.98.140 | — | 300s |
| MX | mail.tilefish.co.uk | 1 | — |
| MX | tilefish-co-uk.mail.protection.outlook.com | 0 | — |
| NS | lewis.ns.cloudflare.com | — | — |
| NS | wally.ns.cloudflare.com | — | — |
| TXT | MS=ms51890128 | — | — |
| TXT | v=DMARC1; p=quarantine; rua=mailto:dmark@tilefish.co.uk; sp=none | — | — |
| TXT | v=spf1 include:spf.protection.outlook.com ~all | — | — |
| TXT | v=spf1 ip4:185.121.133.174 ip4:185.121.133.173 ip4:185.121.133.172 ip4:185.121.133.171 ip4:185.121.133.140 ip4:185.121.133.139 ip4:185.121.133.138 ip4:185.121.133.136 ip4:185.121.133.135 ip4:185.121.133.134 ip4:185.121.133.133 ip4:185.121.133.137 ip4:185.121.133.250 ip4:185.121.133.249 ip4:185.121.133.248 ip4:185.121.133.247 ip4:185.121.133.237 ip4:185.121.133.188 ip4:185.121.133.189 ip4:185.121.133.190 ip4:185.121.133.233 ~all | — | — |
| TXT | v=spf1 ip4:185.121.133.233 ip4:185.121.133.234 ip4:185.121.133.235 ip4:185.121.133.236 ~all | — | — |
| TXT | v=spf1 ip4:185.121.133.233 ip4:185.121.133.236 ip4:185.121.133.235 ip4:185.121.133.234 ~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 Oct 1, 2026 and Oct 3, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- tilefish.co.uk — since at least Oct 3, 2026 → present
- letalon-noir.com — Oct 1, 2026 → Oct 3, 2026
- vizija.nl — Sep 28, 2026 → Oct 1, 2026
- dedicated.vsys.host stable — Jul 2, 2026 → Sep 28, 2026
Network Allocation for 85.137.60.173
- CIDR range
- 85.137.60.0/24
- IP range (int)
- 1,435,057,152 — 1,435,057,407
- Prefix length
- /24
- Organization
- Trunk Networks LTD
- ASN
- AS43180
- ASN name
- Trunk Networks LTD
- Location
- Singapore, Singapore
- Coordinates
- 1.287200, 103.850700
- Accuracy radius
- 20 km
- Postal code
- 17
- Regional Internet Registry
- RIPE
- Allocated
- 2004-11-03
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-02 05:23:35
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 from regional internet registry (RIR) delegation files, re-imported every six hours, for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | UA |
See the full history for 85.137.60.0/24.
Frequently Asked Questions
Who owns 85.137.60.173?
85.137.60.173 is allocated to Trunk Networks LTD (AS43180), registered in Singapore, Singapore.
Where is 85.137.60.173 located?
The geolocation for 85.137.60.173 maps to Singapore, Singapore 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 85.137.60.173 on?
85.137.60.173 belongs to the 85.137.60.0/24 network block announced by AS43180. This range contains 256 addresses.
Does 85.137.60.173 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.
