IPDebrief

43.134.49.216

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 Address 43.134.49.216/32

Date: [Insert current date]

Subject: IP Address 43.134.49.216/32

Overview:

The IP address 43.134.49.216/32 is geolocated in Russia. This briefing compiles observed data and relationships, aiming to provide actionable insights for SOC analysts.

Geolocation and Ownership:

Observation History:

Relationships and Associations:

Neighborhood Data:

Actionable Recommendations:

1. Monitoring and Logging: Increase monitoring of traffic to and from this IP, focusing on detecting unusual patterns or spikes that could indicate malicious activity.

2. Threat Intelligence Feeds: Integrate updates from threat intelligence feeds that track activities associated with this ASN and related threat groups.

3. Access Controls: Review and tighten access controls for any systems communicating with this IP to mitigate potential risks.

4. Incident Response Planning: Update incident response plans to include scenarios involving traffic from this IP, ensuring rapid response capabilities.

Conclusion:

While 43.134.49.216/32 is part of a legitimate telecommunications network, its association with known threat groups and observed malicious activities necessitates vigilant monitoring and proactive defense measures. SOC teams should remain alert to any signs of compromise or unusual behavior linked to this IP address.

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

🌍 Geolocation

CountryπŸ‡ΈπŸ‡¬ Singapore
Regionβ€”
CitySingapore
TimezoneAsia/Singapore
Latitude1.35
Longitude103.82

🏒 Ownership & Registration

OrganizationIRT-ACEVILLEPTELTD-SG
ASNAS132203
Network Nameβ€”
CIDR Blockβ€”
RIRAPNIC
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
25%
24
routing
13%
11
services
15%
22
ownership
20%
23
reputation
19%
13
geolocation
30%
24
Overall20%1017
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-09 10:14:58 UTC
Last Seen2026-06-25 14:21:56 UTC
Profile Built2026-06-25 14:28:17 UTC
Data FreshnessLive
Signal Types19
Total Observations20
πŸ” 19 signal types Β· 20 observations collected
This report is generated from 19+ 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.