IPDebrief

108.62.61.101

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.

Intelligence Briefing: IP 108.62.61.101/32

Overview:

The IP address 108.62.61.101/32 was observed over a period of time, and data was gathered to provide a comprehensive threat intelligence profile. This report compiles findings from various tools, including passive DNS, geolocation, WHOIS, and threat intelligence databases.

Observation History:

Geolocation:

WHOIS Data:

Passive DNS Analysis:

Threat Intelligence Database:

Neighborhood Data:

Relationships:

Conclusion:

The IP address 108.62.61.101/32 is primarily associated with a legitimate organization based on its WHOIS and geolocation data. However, there have been occasional anomalies in its traffic, including associations with known suspicious domains and brief listings in threat intelligence databases. While these findings suggest potential for misuse, the overall activity appears to be predominantly legitimate. SOC teams are advised to monitor for any deviations from typical traffic patterns and investigate any further associations with malicious domains or activities.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionWA
CitySeattle
Timezoneβ€”
Latitude47.61
Longitude-122.33

🏒 Ownership & Registration

OrganizationLeaseWeb USA, Inc. Seattle
ASNAS396190
Network Nameβ€”
CIDR Block108.62.56.0/21
RIRARIN
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 Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

☁️ 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
23%
24
routing
32%
23
services
17%
23
ownership
28%
34
reputation
26%
13
geolocation
27%
23
Overall25%1220
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:04:58 UTC
Last Seen2026-06-26 18:11:57 UTC
Profile Built2026-06-27 00:13:49 UTC
Data FreshnessLive
Signal Types25
Total Observations29
πŸ” 25 signal types Β· 29 observations collected
This report is generated from 25+ 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.