171.161.100.102 is an IPv4 address announced by AS10794, with approximate network location New York, United States. As of November 11, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | Bank of America, National Association |
| ASN | AS10794 |
| Network Name | BOFA-2Z-161 |
| CIDR Block | 171.161.0.0/16 |
| RIR | APNIC |
| Network registration country | United States |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
DNS Posture
Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.
Not assessed: 0 conclusive IP DNS checks.
| spf | Not checked |
| dmarc | Not checked |
| fcrDns | Not checked |
| dnssec | Not checked |
| caa | Not checked |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 80, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | Bank of America Error Page |
🔐 TLS Certificate
| SANs | chat.bankofamerica.comchat.ml.comchat.benefits.ml.comchat.mybenefits.benefits.ml.comchat.merrilledge.comchat-darkpod.bankofamerica.comchat-darkpod.benefits.ml.comchat.mservice-darkpod.bankofamerica.comchat.mservice.bankofamerica.comchat.privatebank.bankofamerica.com |
| Valid From | 2025-11-17T00:00:00+00:00 |
| Valid Until | 2026-12-18T23:59:59+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 396 days |
🛡️ Public Network Snapshot
| Origin ASN | AS10794 |
| Network Prefix | 171.161.100.0/24 |
| Route mapping | Found |
| HSTS | Enabled |
| CSP | Enabled |
| HTTP/2 | Not detected |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 35% | 2 | 2 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 25% | 1 | 2 |
| reputation | 25% | 1 | 1 |
| geolocation | 50% | 2 | 3 |
| Overall | 30% | 8 | 10 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Stale
| First Seen | 2026-10-01 22:22:55 UTC |
| Last Seen | 2026-10-06 04:44:50 UTC |
| Profile Built | 2026-11-11 05:36:13 UTC |
| Data Freshness | Stale |
| Signal Types | 20 |
| Total Observations | 20 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 171.161.100.102
Who owns the IP address 171.161.100.102?
171.161.100.102 is registered to Bank of America, National Association. The address falls within the 171.161.0.0/16 network block. Registration is held at APNIC.
Where is 171.161.100.102 located?
Geolocation data places 171.161.100.102 in New York, US-NY, United States. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 171.161.100.102 malicious or safe?
171.161.100.102 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 171.161.100.102?
Responsive ports observed on 171.161.100.102 include 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.