# 195.178.110.72 — IP Intelligence Summary

195.178.110.72 is an IPv4 address operated by ABUSE DEP (AS48090), geolocated to Reston, Bulgaria. As of November 7, 2026, IPDebrief rates it Moderate Risk (65/100); no anonymizing service was detected.

- Canonical page: https://ipdebrief.com/195.178.110.72
- Last updated: 2026-11-07

## Ownership

- Organization: ABUSE DEP
- Network name: TECHOFF_SRV_LIMITED
- Allocated block: 195.178.110.0/24
- ASN: AS48090 (https://ipdebrief.com/asn/48090)
- Regional registry: RIPE

## Location

- City: Reston
- Region: VA
- Country: Bulgaria
- Time zone: Europe/Sofia

## Network classification

- Infrastructure type: —
- Datacenter / hosting: no
- Residential: no
- Mobile: no
- Anycast: no
- Tor exit node: no
- VPN: no
- Proxy: no

## Risk assessment

- Assessment: Moderate Risk (65/100)
- Blocklist listings: 0
- Suspicious activity indicators: no
- Spam source: no

## Exposed services

- 22/tcp — ssh

## Analyst narrative

**IP Intelligence Briefing: 195.178.110.72**

**Risk Assessment:** Moderate Risk (Score: 65)

**Classification:** Blacklisted Host

**Recommendation:** Block

**Ownership and Location:**

The address belongs to AS48090 (ABUSE DEP) under the organization name TECHOFF_SRV_LIMITED. Registration records indicate the organization is associated with the RIR RIPE. Geolocation data confirmed the location as Amsterdam, Netherlands, with a plausible consensus.

**Threat Indicators:**

The host was listed on three DNS blocklists, contributing to a poor DNS hygiene score of 20. The overall confidence in the threat classification was very low, yet the risk signals were elevated. No Tor exit node activity or known campaign associations were detected.

**Network and Service Data:**

Active observations ranged from 2026-07-17 to 2026-09-04. Scanning identified a single open port on TCP/22 (SSH), running OpenSSH version 8.9p1. No web services, TLS certificates, or email authentication records (SPF/DMARC) were present.

**Environment Context:**

The neighborhood classification was clean, but two threat siblings were identified within the 195.178.110.0/24 subnet. The BGP prefix route was not stable, and RPKI validation was not confirmed.

**Conclusion:**

Due to the elevated risk from multiple threat signals, the action taken was to block the IP address. Firewall rules were recommended for iptables, nginx, and pf to drop traffic from this source.

## Nearby addresses

- 195.178.110.2 (https://ipdebrief.com/195.178.110.2)
- 195.178.110.15 (https://ipdebrief.com/195.178.110.15)
- 195.178.110.18 (https://ipdebrief.com/195.178.110.18)
- 195.178.110.22 (https://ipdebrief.com/195.178.110.22)
- 195.178.110.26 (https://ipdebrief.com/195.178.110.26)
- 195.178.110.28 (https://ipdebrief.com/195.178.110.28)
- 195.178.110.30 (https://ipdebrief.com/195.178.110.30)
- 195.178.110.31 (https://ipdebrief.com/195.178.110.31)
- 195.178.110.33 (https://ipdebrief.com/195.178.110.33)
- 195.178.110.34 (https://ipdebrief.com/195.178.110.34)
- 195.178.110.35 (https://ipdebrief.com/195.178.110.35)
- 195.178.110.36 (https://ipdebrief.com/195.178.110.36)

---

Source: IPDebrief, "195.178.110.72 IP intelligence", https://ipdebrief.com/195.178.110.72, updated 2026-11-07. Assessments are probabilistic.