IPDebrief

222.236.155.146

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 222.236.155.146/32

Overview:

IP address 222.236.155.146, with a netmask of /32, was observed and analyzed using various intelligence tools. The following briefing summarizes findings related to its identity, behavior, and associated risks, providing actionable insights for a Security Operations Center (SOC) analyst.

Identity and Ownership:

Behavioral Analysis:

Relationships and Connections:

Risk Assessment:

Recommendations for SOC Analysts:

1. Implement Monitoring: Increase monitoring of network traffic associated with this IP and its known related peers. Utilize intrusion detection systems to identify and alert on suspicious patterns.

2. Block and Respond: Consider blocking this IP at the network perimeter to prevent potential phishing attacks and unauthorized access.

3. Incident Response Preparation: Develop response plans for potential incidents involving this IP, including forensic investigation and mitigation strategies.

4. User Awareness: Enhance user awareness and training programs to recognize and report phishing attempts associated with this IP.

This intelligence briefing provides a comprehensive view of IP 222.236.155.146/32, enabling SOC teams to take informed actions to mitigate associated threats.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฐ๐Ÿ‡ท South Korea
Region41
CityPyeongtaek-si
TimezoneAsia/Seoul
Latitude35.91
Longitude127.77

๐Ÿข Ownership & Registration

OrganizationIP Manager
ASNAS9318
Network NamebroadNnet-KR
CIDR Block222.232.0.0/13
RIRAPNIC
CountryKR
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 Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

โ˜๏ธ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierUnknown โ€” Insufficient routing data to classify
No specific classification

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpโ€”
443httpstcpโ€”
22sshtcp
Closed Ports25, 3389, 8080, 8443 (3 open / 7 scanned)
Serverโ€”
HTTP Titleโ€”
SSH VersionSSH-2.0-Zyxel SSH server

๐Ÿ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
โš ๏ธ
CN=usg110_B8ECA30FA09D
Issued by CN=usg110_B8ECA30FA09D
Self-signed: Yes
SANsNone
Valid From2016-10-18T14:27:45+00:00
Valid Until2026-10-16T14:27:45+00:00
TLS ProtocolTls12
Cipher SuiteTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period3650 days
Serial Number00A8EDEF5AE1184BCC
ThumbprintB17739359A54F4F3E41710CB66BE2C9675FF4BCC

๐ŸŽฏ Confidence Breakdown

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

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

๐Ÿ“… Observation Timeline ๐Ÿ”„ Fresh

First Seen2026-05-07 23:04:14 UTC
Last Seen2026-06-26 18:11:10 UTC
Profile Built2026-06-25 03:28:03 UTC
Data FreshnessFresh
Signal Types22
Total Observations24
๐Ÿ” 22 signal types ยท 24 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.