IPDebrief

178.210.189.110

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.

IP Intelligence Briefing: 178.210.189.110

*Generated via IPDebrief tools*

---

**Key Risk Indicators**

---

**Threat Observations**

- Firewalled system with no open services or DNS records.

- ICMP blocked (traceroute validation failed).

- Scans detected (June 2, 2026) but no active services found.

- 14 IPs with medium risk (40–55 score), 6 with low risk (25–40).

- One neighbor (178.210.189.172) has zero risk.

---

**Network Relationships**

---

**Actionable Insights**

1. Monitor Subnet: The /24 subnet contains mixed-risk IPs. Prioritize monitoring neighbors with medium risk (e.g., 178.210.189.2, 178.210.189.136).

2. Firewall Rules: Consider blocking ICMP traffic to 178.210.189.110 to prevent reconnaissance.

3. Network Context: Verify if the "avax-admin" ASN is associated with legitimate infrastructure or potential abuse.

4. Threat Correlation: Cross-check with other IPs in the BA-AVAX-20100618 subnet for suspicious activity.

---

**Recommendations**

Note: No immediate remediation required, but continuous monitoring is advised due to the subnet’s mixed risk profile.

---

*Generated by IPDebrief. Data as of June 2026.*

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-NJ
CityNewark
TimezoneAmerica/New_York
Latitude44.88
Longitude18.44

🏒 Ownership & Registration

Organizationavax-admin
ASNAS57888
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
41%
25
routing
13%
11
services
15%
22
ownership
20%
23
reputation
23%
13
geolocation
19%
22
Overall22%1016
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: BA, US

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:03:57 UTC
Last Seen2026-06-22 22:40:08 UTC
Profile Built2026-06-22 22:49:20 UTC
Data FreshnessLive
Signal Types20
Total Observations22
πŸ” 20 signal types Β· 22 observations collected
This report is generated from 20+ 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.