Data as of Nov 13, 2026

158.174.0.0/16

2 anonymizer addresses · <0.01%926 residential-proxy exits · 30 days

Bahnhof AB

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
85% of it

Residential-proxy exits

Proxy exits
926
1.4% of its addresses · 30 days
Always-on exits
60
6.5% of its exits
Spread
157 of 256
/24s with at least one exit
Providers
126
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

229K observations
  • Tor exit · anonymizer
  • Residential
  • Business

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • MrScraper
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • PrivateByte
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyBase
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
2 · Leased from
not leased
3 · Announced by
AS8473 Bahnhof AB
since Jun 2016 · 10.5 yr ago
4 · Use
VPN servicesnamed VPNSecurenamed Tor
Residential

Operators, sellers and brokers

VPN services

NameParentIn 158.174.0.0/16/24s
VPNSecure
1<0.01%
1

Tor

NameParentIn 158.174.0.0/16/24s
TorThe Tor Project
1<0.01%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

158.174.0.0/16

From the registry to its use

  1. May 28, 2016
    Route object
    AS8473 Bahnhof AB
    RIPE route object for AS8473 Bahnhof AB, maintainer BAHNHOF-NCC
  2. Jun 1, 2016– today
    Announced
    AS8473 Bahnhof AB
    Internet provider
  3. today
    Registry record
    Bahnhof AB
    LEGACY
    158.174.0.0/16
  4. today
    Used
    VPNSecure
    VPN
  5. today
    Used
    Tor
    Tor

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
158.174.0.0/1665,536BAHNHOF-AGGREGATEBahnhof AB (ORG-BIA1-RIPE) · SELEGACY—abuse@bahnhof.net
└ 158.174.191.32/304RID-0000581265unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.36/304RID-0000359789unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.40/298RID-0000358097unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.48/304RID-0000285177unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.52/304RID-0001019298unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.56/304RID-0000630342unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.60/304RID-0000798951unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.64/304RID-0000745275unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.68/304RID-0000361578unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.72/298RID-0000759167unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.80/304RID-0000885754unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.84/304RID-0000161941unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.88/304RID-0000982200unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.92/304RID-0000888080unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.96/304RID-0000812349unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.100/304RID-0000635799unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.104/304RID-0000662082unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.108/304RID-0000872580unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.112/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.116/304RID-0000665147unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.120/304RID-0000882519unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.124/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.128/2816GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.144/304RID-0000596165unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.148/312INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.152/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.156/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.160/2816GENERAL-PRIVATE-NET-A498-187Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.176/312RID-0000212901unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.178/312RID-0000614308unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.180/304RID-0000450778unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.184/298GENERAL-PRIVATE-NET-A498-221Dynamic private networkLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.192/312RID-0000626603unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.194/312RID-0000639119unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.196/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.200/304RID-0000197113unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.204/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.208/298RID-0000539020unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.216/304RID-0000650193unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.220/304RID-0000322197unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.192.0/24256GENERAL-PRIVATE-NET-A857-3Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.193.0/24256GENERAL-PRIVATE-NET-A857-4Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.194.0/24256GENERAL-PRIVATE-NET-A857-5Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.195.0/24256GENERAL-PRIVATE-NET-A216-12Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.16/312RID-0000866415unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.24/304RID-0000934644unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.28/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.32/304RID-0001015868unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.36/304RID-0000019035unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.40/298RID-0000163236unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.48/304RID-0000450596unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.52/304RID-0001029525unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.56/298RID-0000490103unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.64/2816RID-0000187229unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.80/298RID-0000321658unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.88/298GENERAL-PRIVATE-NET-A530-18Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.96/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.100/304RID-0000323725unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.104/298RID-0000230423unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.112/2816INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.128/312GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.130/312GENERAL-PRIVATE-NET-A979-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.132/304RID-0000528396unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.136/298RID-0000622933unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.144/304RID-0000904779unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.148/304RID-0000078579unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.152/304RID-0000625191unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.156/304RID-0000325620unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.160/298RID-0000202888unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.168/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.172/304RID-0000336321unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.176/298GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.184/298RID-0000240741unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.196.192/2664GENERAL-PRIVATE-NET-A990-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.197.0/24256GENERAL-PRIVATE-NET-A938-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.0/304RID-0000588478unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.4/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.8/304RID-0000485484unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.12/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.16/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.20/304RID-0000601470unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.24/304RID-0000633885unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.28/304RID-0000758348unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.32/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.36/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.40/304RID-0000634623unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.44/312RID-0000519663unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.46/312RID-0000519663unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.48/298GENERAL-PRIVATE-NET-A979-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.56/304RID-0000445832unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.60/312RID-0000204718unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.62/312RID-0000966944unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.64/2664GENERAL-CORPORATE-NET-A463-13Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.128/2732GENERAL-PRIVATE-NET-A979-3Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.160/304RID-0000514767unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.164/304RID-0000967142unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.168/304RID-0000066239unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.172/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.176/304RID-0000634585unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.182/312INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.184/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.188/304RID-0000335266unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.224/298RID-0000594784unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.232/304RID-0000620600unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.236/304RID-0000983932unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.240/298RID-0000353513unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.248/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.252/312RID-0000299406unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.198.254/312RID-0000598949unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.0/25128GENERAL-CORPORATE-NET-A911-1Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.128/2664GENERAL-CORPORATE-NET-A911-2Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.192/2816GENERAL-PRIVATE-NET-A997-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.208/298RID-0000105219unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.216/298RID-0000129392unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.224/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.228/304RID-0000638428unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.232/298GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.199.248/304RID-0000788032unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.200.0/24256GENERAL-PRIVATE-NET-A315-4Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.201.0/24256GENERAL-PRIVATE-NET-A357-46Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.202.0/24256GENERAL-PRIVATE-NET-A357-47Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.8/304RID-0000977723unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.12/304RID-0000980295unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.16/304RID-0000886386unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.20/304RID-0000304981unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.32/2732RID-0000893098unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.64/2732GENERAL-PRIVATE-NET-A400-75Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.96/304RID-0001009956unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.100/312RID-0000019035unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.102/312RID-0000626603unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.104/304RID-0000287094unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.108/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.112/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.116/304RID-0000631972unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.120/304RID-0000877354unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.124/304RID-0000597260unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.160/298INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.168/298INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.176/298RID-0000458343unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.184/304RID-0000631699unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.188/304RID-0000639110unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.192/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.196/304RID-0000806775unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.200/304RID-0000622022unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.204/304RID-0000516032unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.208/298RID-0000975613unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.216/304RID-0000019909unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.220/304RID-0000905954unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.224/304RID-0000758943unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.228/304RID-0000297239unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.232/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.236/304RID-0000929978unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.203.240/2816GENERAL-PRIVATE-NET-A498-188Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.204.0/24256GENERAL-PRIVATE-NET-A998-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.205.0/24256GENERAL-PRIVATE-NET-A316-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.0/304RID-0000432959unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.4/304RID-0000592611unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.8/304RID-0000436650unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.12/312RID-0000228109unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.14/312RID-0000711176unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.16/298RID-0000431995unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.24/304RID-0000453885unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.28/304RID-0000446603unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.32/304RID-0000993888unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.36/304RID-0000635780unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.40/304RID-0000141786unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.44/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.48/2816GENERAL-PRIVATE-NET-A412-129Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.64/304RID-0000879866unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.68/304RID-0000789338unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.76/312RID-0000626603unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.78/312INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.80/298RID-0000071764unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.88/304RID-0000452362unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.92/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.96/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.100/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.104/298RID-0000517711unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.112/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.116/304RID-0000514985unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.120/298GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.128/304RID-0000285623unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.132/304RID-0000647326unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.136/312RID-0000330906unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.138/312GENERAL-PRIVATE-NET-A99-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.140/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.144/312RID-0000534026unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.146/312RID-0000532879unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.148/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.152/304RID-0000172219unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.156/312RID-0000532879unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.158/312RID-0000445413unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.160/2732GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.200/304RID-0000633912unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.204/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.208/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.212/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.216/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.220/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.206.224/298GENERAL-PRIVATE-NET-A530-19Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous1,201–1,400 of 1,781 · page 7 of 9Next →

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

65,536 addresses
TypeAddressesShareRanges
Residential55,43885%181
Business10,09615%283
Tor exitanonymizer1<0.01%1
VPNanonymizer1<0.01%1

Network & registry

Origin network

AS8473

SE
Name
Bahnhof AB
Type
Internet provider
Registered
Sep 18, 1997
Domain
bahnhof.se
Website
www.bahnhof.net/
Industry
Internet Service Provider (ISP)
Spamhaus ASN-DROP
not listed
VPN servers
127
Tor exits
2