IPDebrief

77.90.185.73

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

IP Intelligence Briefing: 77.90.185.73

Date: 2026-06-07

---

**Key Risk Summary**

---

**Ownership & Geolocation**

- Confirmed as GB (MaxMind) but also observed as IR (Iran) with low confidence.

- No city/region data, suggesting potential spoofing or misconfigured DNS.

---

**Threat Indicators**

- No open ports, TLS certs, or HTTP services detected.

- DNSSEC valid, but no email authentication records (SPF/DKIM).

---

**Network Behavior**

- BGP prefix: 77.90.185.0/24, stable routes (0 changes in 30 days).

- RPKI invalid, but no immediate exploitation risk.

- High-risk siblings: 3 IPs (80โ€“70 risk scores).

- Low-risk siblings: 12 IPs (30โ€“55 risk scores).

- Abusive IPs: 12 IPs (potential compromised hosts).

---

**Observation History**

- Mixed geolocation data (GB/IR) and network ownership records.

- No persistent malicious behavior detected.

- Sudden spikes in subnet abuse density (0.3462).

---

**Actionable Intelligence**

1. Monitor Geolocation Discrepancies: Investigate potential spoofing or misconfigured DNS.

2. Isolate High-Risk Neighbors: Block or monitor IPs with 70+ risk scores (e.g., 77.90.185.16, 77.90.185.37).

3. Verify Network Ownership: Confirm LimitedNetwork-MNTโ€™s legitimacy and subnet management practices.

4. Check for Enumeration: Scan for open ports/services to validate lack of active services.

---

Conclusion:

This IP exhibits moderate risk due to conflicting geolocation data and a subnet with significant abuse density. While no direct threats are detected, its association with high-risk neighbors warrants closer monitoring. SOC teams should prioritize validating geolocation accuracy and isolating suspicious subnets.

Tools Used: IPDebrief Profile, History, Relationships, Neighbors.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฌ๐Ÿ‡ง United Kingdom
RegionUS-NY
CityNew York
TimezoneEurope/London
Latitude35.70
Longitude51.41

๐Ÿข Ownership & Registration

OrganizationLimitedNetwork-MNT
ASNAS213790
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
15%
22
routing
13%
11
services
8%
11
ownership
27%
23
reputation
13%
12
geolocation
19%
22
Overall16%911
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-10 22:18:00 UTC
Last Seen2026-06-26 05:49:46 UTC
Profile Built2026-06-26 06:30:18 UTC
Data FreshnessLive
Signal Types17
Total Observations17
๐Ÿ” 17 signal types ยท 17 observations collected
This report is generated from 17+ 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.