IPDebrief

44.220.188.180

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: 44.220.188.180

Date: June 11, 2026

---

**1. Overview**

---

**2. Threat Indicators**

---

**3. Historical Observations**

---

**4. Network Relationships**

---

**5. Recommendations**

1. Monitor Subnet: Given the moderate abuse density, prioritize monitoring traffic from neighboring IPs in `44.220.188.180/24` for anomalies.

2. Verify DNS Hostname: Investigate `scanner-44-220-188-180.reposify.net` for legitimate use (e.g., CI/CD pipelines) or malicious scanning.

3. Cloud Security: Ensure AWS security groups and firewalls restrict unnecessary access to this compute instance.

4. Subnet Segmentation: Consider isolating high-risk siblings in the subnet to mitigate lateral movement risks.

---

Note: This IP is part of AWS infrastructure, but its subnet contains mixed-risk activity. SOC teams should correlate this data with internal logs and threat feeds for further analysis.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionVA
CityAshburn
TimezoneAmerica/New_York
Latitude39.04
Longitude-77.49

🏒 Ownership & Registration

OrganizationAmazon Data Services Northern Virginia
ASNAS14618
Network NameAMAZON-IAD
CIDR Block44.192.0.0/11
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRscanner-44-220-188-180.reposify.net
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnamesscanner-44-220-188-180.reposify.net

πŸ” DNS Hygiene

Hygiene Score60% (Good)
SPFPresent
DMARCNot configured
FCrDNSVerified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeFirewalled / No Services
Network TierTier 3 β€” Basic operator with some routing infrastructure
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
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
19%
22
routing
19%
12
services
13%
11
ownership
27%
23
reputation
13%
12
geolocation
15%
22
Overall18%912
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-29 12:05:13 UTC
Last Seen2026-06-29 06:29:47 UTC
Profile Built2026-06-29 06:37:53 UTC
Data FreshnessLive
Signal Types20
Total Observations20
πŸ” 20 signal types Β· 20 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.