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.170.20/304RID-0000602997unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.24/298RID-0000951680unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.32/298RID-0000829527unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.40/304RID-0000920013unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.44/304RID-0000232546unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.48/304RID-0000122291unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.52/304RID-0001006813unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.56/298RID-0000459291unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.64/298RID-0001007464unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.72/298RID-0001005132unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.80/304RID-0000858798unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.84/304RID-0000965031unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.88/304RID-0001000666unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.92/304RID-0001007088unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.96/2732GENERAL-PRIVATE-NET-A498-471Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.128/2732GENERAL-PRIVATE-NET-A498-472Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.160/298RID-0000979272unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.168/298RID-0000157061unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.176/304RID-0000913157unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.180/304RID-0001006173unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.184/304RID-0000913157unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.188/304RID-0000913157unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.192/298RID-0001006525unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.200/298RID-0000908032unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.208/298RID-0001006524unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.216/304RID-0001007110unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.220/304RID-0001000669unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.224/304RID-0000365626unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.228/304RID-0000949756unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.232/304RID-0000263526unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.236/304RID-0000997194unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.240/2816RID-0000324224unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.172.0/25128GENERAL-PRIVATE-NET-A950-3Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.172.128/2732RID-0000338503unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.172.160/2816GENERAL-PRIVATE-NET-A988-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.172.176/2816INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.172.192/2664GENERAL-PRIVATE-NETDynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.173.0/24256GENERAL-PRIVATE-NET-A935-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.174.0/23512GENERAL-PRIVATE-NET-A935-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.176.0/25128GENERAL-PRIVATE-NET-A935-3Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.176.128/25128GENERAL-PRIVATE-NET-A971-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.0/2664GENERAL-PRIVATE-NET-A971-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.64/304RID-0000903969unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.68/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.80/2816GENERAL-PRIVATE-NET-A970-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.96/298RID-0000601439unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.104/298INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.112/298INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.120/304RID-0000440083unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.124/304RID-0000599212unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.128/2664GENERAL-PRIVATE-NET-A964-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.192/2732GENERAL-PRIVATE-NET-A498-184Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.177.224/2732GENERAL-CORPORATE-NET-A400-70Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.0/2732GENERAL-CORPORATE-NET-A324-18Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.64/304RID-0000252513unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.68/304RID-0000625892unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.80/304RID-0000624514unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.84/312INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.86/312RID-0000569866unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.88/304RID-0000600124unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.92/312RID-0000600124unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.94/312INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.96/2816GENERAL-PRIVATE-NET-A974-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.112/2816GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.178.128/25128GENERAL-PRIVATE-NET-A972-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.0/304RID-0000488981unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.4/304RID-0000016609unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.8/304RID-0001019314unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.12/304RID-0000776125unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.16/312RID-0000809970unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.18/312RID-0000878830unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.20/304RID-0000330906unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.24/304RID-0000822785unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.28/304RID-0000434008unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.32/2732GENERAL-PRIVATE-NET-A498-185Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.128/2816GENERAL-PRIVATE-NET-A973-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.144/304RID-0000902441unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.148/304RID-0000630920unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.152/304RID-0000882747unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.156/312RID-0000167234unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.158/312RID-0000511396unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.160/2732GENERAL-CORPORATE-NET-A400-71Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.192/298RID-0000106661unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.200/298RID-0000959363unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.208/304RID-0000883462unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.212/304RID-0000640276unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.216/304RID-0000122155unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.220/304RID-0000076282unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.224/298RID-0000461566unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.232/304RID-0000611114unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.236/312RID-0000445156unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.238/312RID-0000365162unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.179.240/2816RID-0000169187unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.180.0/24256GENERAL-PRIVATE-NET-A980-115Dynamic private networkLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.64/298RID-0000626424unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.72/304RID-0001041153unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.76/304RID-0000186582unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.80/298RID-0000455206unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.88/304RID-0000849681unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.92/304RID-0000878439unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.96/304RID-0000469030unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.100/304RID-0000193127unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.104/298RID-0000818298unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.112/304RID-0000736425unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.116/304RID-0000999480unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.120/298RID-0000822074unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.192/2816RID-0000327091unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.208/298RID-0000327091unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.216/298RID-0000297239unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.224/304RID-0000335474unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.228/304RID-0000344587unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.232/304RID-0000146431unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.181.236/304RID-0000326196unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.0/304RID-0000262738unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.4/304RID-0000539017unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.8/304RID-0000603195unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.16/304RID-0000889213unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.20/304RID-0000161197unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.32/2732GENERAL-CORPORATE-NET-A444-12Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.64/298RID-0000608803unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.72/298RID-0000583108unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.80/304RID-0000288035unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.84/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.88/298GENERAL-PRIVATE-NET-A530-14Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.96/2816GENERAL-CORPORATE-NET-A295-2Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.112/304RID-0000460120unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.116/304RID-0000628486unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.120/298GENERAL-PRIVATE-NET-A530-15Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.128/312RID-0000181964unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.130/312INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.132/304RID-0000977202unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.136/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.140/304RID-0000942199unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.144/304RID-0000883188unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.148/304RID-0000985019unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.152/298GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.160/304RID-0000597119unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.164/304RID-0000242725unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.180/304RID-0000626967unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.182.224/2732GENERAL-PRIVATE-NET-A498-186Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.0/304RID-0000768830unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.4/304RID-0000929306unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.8/298GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.24/304RID-0000632637unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.28/304RID-0000725281unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.32/304RID-0000632338unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.36/304RID-0000748033unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.40/304RID-0000086374unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.44/304RID-0000632418unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.48/312INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.50/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.56/298RID-0000620351unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.64/2732GENERAL-PRIVATE-NET-A986-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.96/298RID-0000730812unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.104/304RID-0000242349unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.108/304RID-0000757800unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.112/304RID-0000690587unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.120/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.124/304RID-0000267782unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.128/304RID-0000726444unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.132/304RID-0000270995unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.136/304RID-0000871054unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.140/304RID-0000907861unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.144/304RID-0000630522unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.148/304RID-0000602157unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.152/298GENERAL-PRIVATE-NET-A530-16Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.160/298RID-0000283598unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.168/304RID-0000507310unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.172/304RID-0001064550unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.176/2816GENERAL-PRIVATE-NET-A985-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.192/2732GENERAL-PRIVATE-NET-A985-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.224/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.228/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.236/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.240/304RID-0000523521unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.244/304RID-0000921893unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.188.248/298RID-0000634323unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.189.0/24256RID-0000020483unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.0/304RID-0000628080unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.4/304RID-0000633631unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.8/304RID-0000275977unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.12/304RID-0000633385unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.48/304RID-0000157753unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.52/304RID-0000051004unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.56/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.60/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.64/304RID-0001018537unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.68/304RID-0000199110unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.72/298RID-0000828355unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.80/304RID-0000642852unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.84/304RID-0000636853unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.88/298GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.190.96/2732GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.0/298GENERAL-PRIVATE-NET-A530-17Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.8/304RID-0001022988unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.12/304RID-0000167125unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.16/304RID-0000901496unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.20/304RID-0000752836unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.24/304RID-0000761810unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.191.28/304RID-0000886447unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous1,001–1,200 of 1,781 · page 6 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