The IP address 198.202.176.111 was assigned to Stripe, Inc. under ASN 16509 within the 198.202.176.0/24 block. The profile indicated a Low Risk status with a risk score of 20. Operational analysis identified the host as an nginx Web Server exposing HTTP (port 80) and HTTPS (port 443) services, utilizing a valid DigiCert TLS certificate for the stripe.com domain. Geolocation data placed the location in the United States, yet a contradiction existed between the claimed geographic coordinates and measured Round-Trip Time (RTT) physics. No threat indicators, blacklist entries, or active campaign associations were detected. The surrounding subnet was classified as clean with no threat siblings observed. Due to signal contradictions regarding geographic plausibility, monitoring was recommended. Data freshness indicated live observation as of September 10, 2026.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Stripe, Inc. |
| ASN | AS16509 |
| Network Name | STRIP-11 |
| CIDR Block | 198.202.176.0/24 |
| RIR | ARIN |
| 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 Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Not configured |
βοΈ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown β Insufficient routing data to classify |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | β |
| 443 | https | tcp | β |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | nginx |
| HTTP Title | β |
π TLS Certificate
| SANs | *.stripe.comstripe.com |
| Valid From | 2026-09-08T00:00:00+00:00 |
| Valid Until | 2026-12-10T23:59:59+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384ECDSA |
| Validity Period | 93 days |
| Serial Number | 09BD40F02298E440B80701C1320FC465 |
| Thumbprint | 4914A5CF05DDBA459660BF5D4F51D8AE57D58C5D |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 27% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 27% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 35% | 2 | 3 |
| Overall | 24% | 10 | 15 |
| Data Coherence | Mostly Consistent (80%) β 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-09-10 15:07:26 UTC |
| Last Seen | 2026-09-20 00:31:33 UTC |
| Profile Built | 2026-09-23 06:29:35 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 27 |
Full dossier details are available via our API.