IPDebrief

31.57.184.116

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON ๐Ÿ”ง Full Actions API
๐Ÿค– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP Intelligence Briefing: 31.57.184.116

Date: 2026-06-18

---

**1. Risk Profile**

- Country: United Arab Emirates (AE)

- Region/City: Conflicting data (Illinois, Chicago) vs. UAE coordinates (latitude 23.42, longitude 53.85). Likely geolocation error.

---

**2. Observation History**

- Confidence: 0.21 (low).

- Signal Type 15: Mixed data with 6 dimensions analyzed, but low overall confidence.

- Signal Type 6855: Geolocation inferred as UAE with 0.35 confidence.

---

**3. Network Relationships**

- Subnet 31.57.184.0/24 classified as "high_abuse" with 8 out of 14 sibling IPs flagged as threats.

- Abuse Density: 57.14% (high risk).

- Inherited Risk: 19 (likely from subnet abuse).

---

**4. Neighborhood Analysis**

- High Risk: 2 IPs (e.g., 31.57.184.42, 31.57.184.56).

- Medium Risk: 11 IPs (e.g., 31.57.184.20, 31.57.184.104).

---

**5. Security Recommendations**

- iptables: `iptables -A INPUT -s 31.57.184.116 -j DROP`

- nftables: `nft add rule inet filter input ip saddr 31.57.184.116 drop`

- Cloudflare WAF: Block IP with rule `{ "action": "block", "expression": "ip.src eq 31.57.184.116" }`.

---

**6. Summary**

1. Block the IP using provided firewall rules.

2. Investigate subnet 31.57.184.0/24 for shared infrastructure risks.

3. Validate geolocation data for accuracy.

Note: No direct malicious activity detected, but the subnet's high abuse density warrants cautious monitoring.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

๐ŸŒ Geolocation

Country๐Ÿ‡ฆ๐Ÿ‡ช United Arab Emirates
RegionIllinois
CityChicago
TimezoneAsia/Dubai
Latitude23.42
Longitude53.85

๐Ÿข Ownership & Registration

OrganizationAbuse
ASNAS197769
Network Nameโ€”
CIDR Blockโ€”
RIRRIPE
Countryโ€”
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo โ€” PTR hostname does not resolve back to this IP (weak signal)

๐Ÿ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

โ˜๏ธ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown โ€” Insufficient routing data to classify
No specific classification

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverโ€”
HTTP Titleโ€”

๐Ÿ” TLS Certificate

๐Ÿ”’
No certificate
Issued by โ€”
N/A
SANsNone
Valid Fromโ€”
Valid Untilโ€”

๐ŸŽฏ Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
26%
23
routing
13%
11
services
8%
11
ownership
24%
23
reputation
26%
13
geolocation
21%
22
Overall20%913
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-07 23:04:15 UTC
Last Seen2026-06-23 10:01:35 UTC
Profile Built2026-06-23 10:16:07 UTC
Data FreshnessLive
Signal Types18
Total Observations20
๐Ÿ” 18 signal types ยท 20 observations collected
This report is generated from 18+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API ๐Ÿ”ง Actions API ๐Ÿ“ง Enterprise Access

โ„น๏ธ About This Report

All data shown is publicly available network metadata โ€” IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.