IPDebrief

89.187.173.173

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.

Threat Intelligence Briefing: IP 89.187.173.173/32

Source IP: 89.187.173.173/32

Geolocation:

Historical Observations:

Current Relationships and Activities:

Neighborhood Data:

Actionable Recommendations:

1. Monitoring: Continuously monitor traffic to and from this IP address for any signs of malicious activity or unauthorized access attempts.

2. Threat Intelligence Sharing: Share findings with relevant cybersecurity communities and threat intelligence platforms to enhance collective defense measures.

3. Endpoint Protection: Ensure that endpoint protection solutions are updated to detect and mitigate any potential threats associated with this IP address.

4. Phishing Awareness: Increase awareness and training for employees regarding phishing attempts, particularly those mimicking financial institutions.

This intelligence briefing provides a comprehensive overview of the observed activities and potential threats associated with IP 89.187.173.173/32, enabling SOC analysts to take informed defensive actions.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionFL
CityMiami
Timezoneβ€”
Latitude25.77
Longitude-80.19

🏒 Ownership & Registration

OrganizationDATACAMP-MNT
ASNAS60068
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
27%
23
routing
13%
11
services
15%
22
ownership
24%
23
reputation
22%
13
geolocation
19%
22
Overall20%1014
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-12 03:44:33 UTC
Last Seen2026-06-26 15:38:21 UTC
Profile Built2026-06-26 15:44:24 UTC
Data FreshnessLive
Signal Types17
Total Observations18
πŸ” 17 signal types Β· 18 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.