IPDebrief

54.38.147.91

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.

As a large language model, I cannot provide real-time intelligence or access current databases to gather specific information about IP addresses or any other real-time data. However, I can guide you on how to conduct such an analysis using best practices and available tools. Here's a general approach to creating a threat intelligence briefing for an IP address:

Steps for Conducting a Threat Intelligence Analysis

1. Initial IP Reconnaissance:

- Use online tools like Whois lookup services (e.g., WHOIS.net, ICANN WHOIS) to gather basic information about the IP address, such as its owner, registration date, and contact details.

- Check if the IP is listed in any public threat intelligence databases (e.g., VirusTotal, AbuseIPDB) to see if it has been associated with malicious activity.

2. Historical Data and Observation:

- Investigate historical data using threat intelligence platforms that track IP reputation over time (e.g., Recorded Future, ThreatConnect).

- Analyze logs and network traffic data from your organization's infrastructure to see if there have been any past interactions with the IP.

3. Relationships and Behavioral Analysis:

- Use network monitoring tools to observe current and past traffic patterns associated with the IP.

- Check if the IP has been part of any known botnets or has been used in DDoS attacks. Tools like AlienVault OTX can provide insights into such behaviors.

4. Neighborhood Analysis:

- Identify other IPs hosted by the same organization or ISP (e.g., using IP geolocation services like MaxMind) to understand the surrounding network environment.

- Check if neighboring IPs have been flagged for suspicious activity, which might indicate a compromised network.

5. Threat Context and Indicators:

- Gather context about the IP's geographic location and time zones to understand potential threat actors.

- Look for any known vulnerabilities or exploits associated with services hosted on the IP.

Sample Threat Intelligence Narrative

Threat Intelligence Briefing for IP 54.38.147.91/32

- Registered to: [Owner Information]

- Location: [Geographical Data]

- Associated Organization: [ISP or Hosting Provider]

- Historical Observations: [Summary of past interactions and threat intelligence findings]

- Malicious Activity: [Any associations with malware, phishing, or botnets]

- Traffic Patterns: [Description of observed network traffic behaviors]

- Neighboring IPs: [List of IPs in the same subnet or organization]

- Threats in Neighborhood: [Any known threats or vulnerabilities affecting neighboring IPs]

- Monitor for suspicious activity from this IP.

- Implement network segmentation to isolate traffic to/from this IP.

- Update firewall rules to block or restrict access if malicious activity is confirmed.

Recommendations:

This approach should help you gather and present threat intelligence in a structured manner, suitable for analysis by a Security Operations Center (SOC) team. Always ensure compliance with legal and organizational policies when conducting such analyses.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฌ๐Ÿ‡ง United Kingdom
RegionEngland
CityLondon
TimezoneEurope/London
Latitude48.86
Longitude2.34

๐Ÿข Ownership & Registration

OrganizationAhrefs Pte Ltd Dmytro
ASNAS16276
Network Nameโ€”
CIDR Blockโ€”
RIRARIN
Countryโ€”
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTRproxy-uk005-san91.ahrefs.net
Forward ConfirmedNo โ€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesproxy-uk005-san91.ahrefs.net

๐Ÿ” DNS Hygiene

Hygiene Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

โ˜๏ธ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeFirewalled / No Services
Network TierHosting โ€” Infrastructure provider without advanced routing
CloudHosting

๐Ÿ”Œ 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%
24
routing
13%
11
services
20%
23
ownership
20%
23
reputation
28%
13
geolocation
30%
23
Overall23%1017
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) โ€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
โš  Geo sources disagree on country: FR, GB

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-07 23:04:28 UTC
Last Seen2026-06-27 07:54:40 UTC
Profile Built2026-06-28 02:00:59 UTC
Data FreshnessLive
Signal Types22
Total Observations30
๐Ÿ” 22 signal types ยท 30 observations collected
This report is generated from 22+ 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.