IP cleanliness report

176.46.132.72

Multi-source IP cleanliness, network ownership, and risk signals.

Checked:2026-10-18 10:11:15 AT&T Services, Inc. · AS7018 United States · New York City · High confidence
39
REPUTATION
Higher scores mean fewer current risk signals
01 · Executive finding

High-risk signals

Not recommended for IP-quality-sensitive sign-in, registration, payment, or long-lived account sessions. Replace the exit IP and retest first.

欺诈或攻击风险偏高
Checked2026-10-18 10:11:15 Score scale0–100 Data coverage16 data sources
02 · Key findings

Risk and clear signals

Review signals that need attention first, followed by key clear findings; only decision-useful evidence is shown here.

Key evidence is ordered by impact; the complete scoring ledger can be expanded in Score composition below.
Needs attention2
IP TypeResidential/ISP (1 consistent type signals) 37 / 40
Scamalytics ScoreHigh(83) ❌ 0 / 5
Key passed checks6
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
Proxy Detection3 pass ✅ 7 / 7
proxycheck RiskLow(Risk=0) ✅ 5 / 5
Tor DetectionNot Tor ✅ 5 / 5
VPN Detection3 pass ✅ 8 / 8
03 · Score composition

How the score was calculated

Shows the base score, risk deductions, clean confirmation, and final score; the full scoring ledger stays collapsed until needed.

Base89
Deductions-10.6
Clean confirmation0
Final39
Risk-signal deductionsElevated fraud or attack risk-10.6
IP TypeResidential/ISP (1 consistent type signals)37 / 40
Scamalytics ScoreHigh(83) ❌0 / 5
All score checksSources 16/16 · Ceiling 93
Deduction:Elevated fraud or attack riskDeducted directly from the base scoreDeducted-10.6
IP TypeResidential/ISP (1 consistent type signals)Pass37 / 40
VPN Detection3 pass ✅Pass8 / 8
Proxy Detection3 pass ✅Pass7 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreHigh(83) ❌Risk0 / 5
proxycheck RiskLow(Risk=0) ✅Pass5 / 5
Abuse HistoryNo match—
IPsum threat intelligenceNo match—
Feodo TrackerNo match—
Spamhaus DROPNo match—
DShieldNo match—
Threat-feed consensusNo multi-source confirmationNo match—
BGP RouteAnnounced and visible ✅Pass2 / 2
Port ExposureNo reliable exposure dataNo match—
Subnet QualityNo reliable neighbor dataNo match—
Bot DetectionNot bot ✅Pass1 / 1
04 · Network profile

Network identity and location

All geolocation fields remain visible; confidence represents source agreement, not GPS-level physical accuracy.

IP Type Residential / ISP
Proxy Status No Proxy Detected
Network AT&T Services, Inc. (AS7018)
Location US · New York · New York City (High confidence)
Location typeStandard network estimate5 geolocation sources returned
Country / regionHigh confidence
United States (US)4/4 available sources agree
State / provinceHigh confidence
New York3/3 available sources agree
City estimateHigh confidence
New York City3/3 available sources agree
Postal codeLow confidence
100011/2 available sources agree
TimezoneHigh confidence
America/New_York3/3 available sources agree
Reference coordinatesHigh confidence
40.71, -74.013/5 available sources agree · coordinate spread about 0 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoUSNew YorkNew York City40.71, -74.01America/New_York
IP2LocationUSNew YorkNew York City40.71, -74.01America/New_York
ipapi.comUSWashingtonRedmond (Downtown)47.68, -122.13America/Los_Angeles
proxycheck.ioUSWashingtonRedmond (Downtown)47.67, -122.12America/Los_Angeles
ipapi.isUnited StatesNew YorkNew York City40.71, -74.01America/New_York
05 · Data sources

Source coverage and completion

Lists each source used in this check and its completion state by role; scoring evidence and individual matches remain in the scoring and evidence sections.

Complete16
Not applicable0
Unavailable0
Sources16

Registry1

RIR RDAPUS · MNTTR · 176.46.132.0/24 · 176.46.132.0 - 176.46.132.255Complete

Network identity3

IPinfoUS · AS2914 NTT America, Inc.Complete
IP2LocationUS · AS2914 · Farahoosh Dena PLCComplete
ipapi.isUnited States · AS2914 · NTT America, Inc.Complete

Routing and ASN2

RIPEstatAS2914 · 176.46.132.0/24 · RIPE · Visibility 99.7%Complete
Team CymruAS2914 · 176.46.132.0/24 · NTT-DATA-2914 - NTT America, Inc., USComplete

Proxy and reputation3

proxycheck.ioUnited States · Mnttr · business · Risk 0Complete
ipapi.comUS · AS7018Complete
ScamalyticsFraud 83/100Complete

Threat intelligence6

Spamhaus DROPnot_listedComplete
IPsumnone · 0 feedsComplete
Feodo TrackerComplete
Tor ProjectComplete
DShieldComplete
Blocklist.deComplete

Internet exposure1

Shodan InternetDBComplete
06 · Report appendix

Report methodology and field snapshot

ScoringFixed-weight aggregation with separate risk deductions
GeolocationDatabase consensus, not the device’s physical location
Snapshot time2026-10-18 10:11:15
06.1 · Report field snapshot
FieldValue
IP Address176.46.132.72
Reputation Score39/100
Cleanliness LevelElevated signals
IP TypeResidential / ISP
CountryUnited States
State / provinceNew York
City estimateNew York City · High confidence · 3/3 available sources agree
Postal code10001
TimezoneAmerica/New_York
Reference coordinates40.71, -74.01
ISPAT&T Services, Inc.
ASNAS7018
Proxy/VPNNo
Proxy TypeNone
Datacenter IPNo
Tags欺诈或攻击风险偏高
Last Checked2026-10-18 10:11:15
06.2 · Scoring and interpretation
What does the score for 176.46.132.72 mean?

A score of 39/100 means several sources returned signals requiring attention. Exact labels, check time, and original sources are listed in the report.

What type of IP is this?

176.46.132.72 is a residential IP on AT&T Services, Inc. (AS7018) in US New York City.

How is the cleanliness score calculated?

The system queries 16 data sources covering proxy/VPN classification, malicious ranges, threat intelligence, ASN, and port exposure. Evidence is combined with fixed weights into a 0-100 score and is generated only when completeness requirements are met.

What score is safe?

There is no universal safe score for every website. IPRisk summarizes proxy, blacklist, network-type, and threat-intelligence signals; each service has its own rules and may use data not shown here.

06.3 · Related samples on the same ASN

This IP returned multiple risk signals. After changing the exit, return to the IP cleanliness check to retest it, then use the Environment Scan to confirm browser routing consistency.

Check another IP Check browser routes