84.18.217.65
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 (22y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Enterprise allocation +4
- Trust score 85 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- catalyst2.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 10800 s
- Reverse DNS last checked
- 2026-09-22 20:17 UTC
- Forward DNS last checked
- 2026-09-22 20:17 UTC
Forward DNS records for catalyst2.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 85.233.172.163 | — | 328s |
| MX | catalyst2-com.mail.protection.outlook.com | 5 | — |
| NS | ns1.catalyst2.net | — | — |
| NS | ns2.catalyst2.net | — | — |
| TXT | 29fm9ck4chfghv9w901gmf9nz68qkvjg | — | — |
| TXT | 3ltw9zsj441bdl7ykdfy1d3hys7c1gr8 | — | — |
| TXT | 9tgkxnpvyfsm42mws9sr0ncsly9q9hwr | — | — |
| TXT | MS=5F7AFA339BFB753355AE162A433EAE1083F17A96 | — | — |
| TXT | _18j09mdq7r8u81rnjgetzdjxygto3gn | — | — |
| TXT | _1nuabgo80bbzyu18fte5pg5p6qykef8 | — | — |
| TXT | _22gqbesyp66gcade08058qptl8nwooa | — | — |
| TXT | _2p5246wbjjl244vpgb4ftej2mvnj98h | — | — |
| TXT | _64djbhkzhkle4wbplg3lftwv84fgyym | — | — |
| TXT | _izkrn0p7nik6xstn4cldqf9kkv4t6ya | — | — |
| TXT | _pv0csab2eqt5oudgc7d52u4v9vc2ywx | — | — |
| TXT | _rdreov0w9h9nz4zwfhcli0ef0xrt9nu | — | — |
| TXT | atlassian-domain-verification=QEaTRSaAw00VJgEdUwXJ9dYvROG1hC656hgsuHMLzTKPQhfMBVUk0aHqE62BDsIq | — | — |
| TXT | atlassian-sending-domain-verification=f40f24f6-5670-4106-9f66-3ec281128577 | — | — |
| TXT | f3sjp570jqxtw3zp3ws346tqx8srfch6 | — | — |
| TXT | google-site-verification=mqZnlGVBmktjhzmzOLBTo-zFt5p3RAq8a3CqwLwgP34 | — | — |
| TXT | google-site-verification=s9-U2182Phxhf8LXNSw2o2siWAQjdOvAupPNu4yqGpU | — | — |
| TXT | gp383hy2n0j6sxjxjhvxw9cj0wgy4fh9 | — | — |
| TXT | knk2zzms3lsptnpkwzdvc12jbh5b0xtf | — | — |
| TXT | loaderio=e19d92b18fbcd2680ae272899d63a317 | — | — |
| TXT | lr6944xq03gz6g7h9s4nb63mldkcwzzj | — | — |
| TXT | mtws8gklxl4qmb287m1n7ffj2g2kkmjx | — | — |
| TXT | p1rcml1bs9k4kkblwrnqlggf71dwnhtz | — | — |
| TXT | qwp4nvjwk6dt0q6j9pjy6xpkdfxy693p | — | — |
| TXT | v=DMARC1; p=none; sp=none; rua=mailto:re+c7c7b89c2674@inbound.dmarcdigests.com; ruf=mailto:forensicreports@catalyst2.com; aspf=r; fo=1; pct=100 | — | — |
| TXT | v=spf1 mx a include:_spf.quotientapp.com include:spf.protection.outlook.com ~all | — | — |
| TXT | yl0p709xytt94cvfg2lqtn27kkvg96zw | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 84.18.217.65
- CIDR range
- 84.18.208.0/20
- IP range (int)
- 1,410,519,040 — 1,410,523,135
- Prefix length
- /20
- Organization
- Team Blue Carrier Limited
- ASN
- AS29636
- ASN name
- Team Blue Carrier Limited
- Location
- United Kingdom
- Coordinates
- 51.496400, -0.122400
- Accuracy radius
- 200 km
- Regional Internet Registry
- RIPE
- Allocated
- 2004-08-16
- Data source(s)
- maxmind_asn, ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-07-10 00:20: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 84.18.217.65?
84.18.217.65 is allocated to Team Blue Carrier Limited (AS29636), registered in United Kingdom.
Where is 84.18.217.65 located?
The geolocation for 84.18.217.65 maps to United Kingdom 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 84.18.217.65 on?
84.18.217.65 belongs to the 84.18.208.0/20 network block announced by AS29636. This range contains 4,096 addresses.
Does 84.18.217.65 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.
