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 (31y) +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)
- ivanhoecambridge.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-09-12 23:49 UTC
Forward DNS records for ivanhoecambridge.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 108.163.144.117 | — | 3600s |
| MX | ivanhoecambridge-com.mail.protection.outlook.com | 5 | — |
| MX | ms60066491.msv1.invalid | 32767 | — |
| NS | dom.ns.cloudflare.com | — | — |
| NS | sima.ns.cloudflare.com | — | — |
| TXT | 63DbxCfuZJANaRredllJEUNTrRN3/JZyn129B/Vi2UAmKRrRFAu/T/ARWEGNFbX9t4WWMYZS7rTfJpoUU4ZCEQ | — | — |
| TXT | MS=ms60066491 | — | — |
| TXT | MS=ms82381332 | — | — |
| TXT | a3hiamkbjs5isve8rdk3m7qr24 | — | — |
| TXT | adobe-sign-verification=5b1d4f0ff1a487cc1d6b0720894fb13f | — | — |
| TXT | apple-domain-verification=TZeeBx1kMnTXAp2M | — | — |
| TXT | cisco-ci-domain-verification=602a48061f149da8ccf041f600072602af1553093b1298f1335d55987175f17d | — | — |
| TXT | detectify-verification=0d89f24717a31138d64b278dc9b1a5ab | — | — |
| TXT | facebook-domain-verification=mxxqbwkekmtmu65dcpej2unxl8ut98 | — | — |
| TXT | google-gws-recovery-domain-verification=46218228 | — | — |
| TXT | google-site-verification=JTH25ZCjeOthmeGVT4JVzZXi3Q5Ita1cvT_rDndMG6o | — | — |
| TXT | google-site-verification=fiFp-veOTySuX-WnZVm59ItwEu6d4nJweqiwkKq1Hk0 | — | — |
| TXT | google-site-verification=hyX8JMmjz0LmtFmmBKw30SQfGYzcsp5So-JnQ6NCEVU | — | — |
| TXT | gt9oiem3lk2ngse5btfd7bprk4 | — | — |
| TXT | ibmid=3702c859-3c65-4ecc-8a80-546a134aa0c7 | — | — |
| TXT | onetrust-domain-verification=778b4ba10eb14a86a164c8232fdfa4d4 | — | — |
| TXT | teamviewer-sso-verification=43aad84c90c84a63a4d0cf88ba9bb975 | — | — |
| TXT | v=DMARC1; p=quarantine; rua=mailto:dmarc_agg@vali.email; | — | — |
| TXT | v=spf1 mx ip4:206.172.6.233 ip4:206.172.6.234 ip4:206.172.6.236 ip4:207.35.136.41 ip4:160.34.236.14 ip4:204.136.15.135 ip4:159.135.239.140 ip4:72.55.128.236 include:spf.protection.outlook.com include:servers.mcsv.net include:spf.boreal-is.com include:performind.com -all | — | — |
| TXT | vmware-cloud-verification-07e5eb6d-43a2-4772-b7b7-47f9e3908e6a | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 206.47.222.3
- CIDR range
- 206.47.222.0/27
- IP range (int)
- 3,459,243,520 — 3,459,243,551
- Prefix length
- /27
- Organization
- Bell Canada
- ASN
- AS577
- ASN name
- Bell Canada
- Location
- Wheatley, Ontario, Canada
- Coordinates
- 42.097300, -82.446000
- Accuracy radius
- 10 km
- Postal code
- N0P
- Regional Internet Registry
- ARIN
- Allocated
- 1995-07-07
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-08-18 04:09:20
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 | New Allocation | — | CA |
See the full history for 206.47.192.0/18.
Frequently Asked Questions
Who owns 206.47.222.3?
206.47.222.3 is allocated to Bell Canada (AS577), registered in Wheatley, Canada.
Where is 206.47.222.3 located?
The geolocation for 206.47.222.3 maps to Wheatley, 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 206.47.222.3 on?
206.47.222.3 belongs to the 206.47.222.0/27 network block announced by AS577. This range contains 32 addresses.
Does 206.47.222.3 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.
