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
159 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.4 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.44.48/298RID-0000107592unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.56/304RID-0001015098unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.60/304RID-0000804517unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.64/2732RID-0000751789unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.96/298RID-0000778602unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.104/298RID-0001011994unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.112/2816RID-0001011994unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.128/298RID-0001011994unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.136/298RID-0001014567unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.144/304RID-0001017265unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.148/304RID-0000977685unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.152/298RID-0001013548unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.160/298RID-0001017472unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.168/304RID-0000914943unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.172/304RID-0001014148unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.176/304RID-0001016860unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.180/304RID-0000771108unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.184/298RID-0001017022unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.232/298RID-0000301824unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.240/304RID-0001018535unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.244/304RID-0000962320unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.248/304RID-0001025754unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.252/304RID-0000853595unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.45.0/24256GENERAL-PRIVATE-NET-A412-126Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.0/304RID-0000235529unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.4/304RID-0000848519unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.8/304RID-0000969740unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.12/304RID-0000471952unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.24/304RID-0000971155unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.28/304RID-0000969317unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.48/298RID-0000879631unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.56/304RID-0000970947unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.60/304RID-0000161119unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.64/304RID-0000161119unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.68/304RID-0000970121unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.72/298RID-0000507857unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.80/304RID-0000189123unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.84/304RID-0000809800unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.88/298RID-0000201974unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.96/304RID-0000966394unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.100/304RID-0000958034unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.104/298RID-0000971083unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.112/298RID-0000643969unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.120/298RID-0000935785unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.46.128/2664GENERAL-CORPORATE-NET-A137-267Dynamic corporate networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.47.0/24256GENERAL-PRIVATE-NET-A240-21Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.48.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.49.0/25128GENERAL-PRIVATE-NET-A163-7Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.49.160/2732GENERAL-CORPORATE-NET-A412-37Dynamic corporate networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.49.192/2732GENERAL-CORPORATE-NET-A137-270Dynamic corporate networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.49.224/2732GENERAL-PRIVATE-NET-A498-90Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.50.0/23512GENERAL-PRIVATE-NET-A240-19Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.52.160/2816RID-0000312807unknownLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.52.176/2816RID-0000312807unknownLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.52.192/2664RID-0000124507unknownLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.0/298RID-0000976336unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.8/298RID-0000433585unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.16/304RID-0000606215unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.20/304RID-0000941211unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.24/304RID-0000770216unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.28/304RID-0000447038unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.80/2816RID-0000234485unknownLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.96/298GENERAL-PRIVATE-NET-A498-89Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.53.128/25128GENERAL-PRIVATE-NET-A217-3Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.54.0/24256GENERAL-PRIVATE-NET-A444-13Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.0/298RID-0000605895unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.8/298GENERAL-PRIVATE-NET-A872-1Dynamic private networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.16/2816GENERAL-PRIVATE-NET-A947-1Dynamic private networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.64/2732GENERAL-PRIVATE-NET-A872-2Dynamic private networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.96/2816GENERAL-PRIVATE-NET-A872-3Dynamic private networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.112/298GENERAL-CORPORATE-NETDynamic corporate networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.120/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.124/304RID-0000621375unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.128/312RID-0000780886unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.130/312INFRA-AW-BIABInfrastructure networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.132/312RID-0000953060unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.134/312INFRA-AW-BIABInfrastructure networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.136/312RID-0000284185unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.138/312INFRA-AW-BIABInfrastructure networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.140/312RID-0000752769unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.142/312INFRA-AW-BIABInfrastructure networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.144/312INFRA-AW-BIABInfrastructure networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.146/312INFRA-AW-BIABInfrastructure networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.148/304RID-0000616013unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.152/312RID-0000330906unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.156/304RID-0000558176unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.160/304RID-0000330906unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.166/312RID-0000560158unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.176/304RID-0000335163unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.184/312RID-0000313562unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.186/312RID-0000614308unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.188/304RID-0000019909unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.192/2732GENERAL-PRIVATE-NET-A498-220Dynamic private networkLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.224/298RID-0000601620unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.232/298RID-0000441316unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.240/304RID-0000361242unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.248/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.55.254/312GENERAL-CORPORATE-NETDynamic corporate networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.56.0/25128GENERAL-CORPORATE-NET-A137-268Dynamic corporate networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.57.0/24256GENERAL-PRIVATE-NET-A251-11Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.58.0/23512GENERAL-PRIVATE-NETDynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.60.0/24256GENERAL-PRIVATE-NET-A857-1Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.32/2732GENERAL-PRIVATE-NET-A498-165Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.64/2732GENERAL-PRIVATE-NET-A498-166Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.128/312RID-0000060090unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.130/312RID-0000908012unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.132/304RID-0000262599unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.136/304RID-0000549461unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.140/304RID-0000019909unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.144/304RID-0000585996unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.148/304RID-0000558337unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.152/304RID-0000492952unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.156/304RID-0000928613unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.160/298RID-0000299406unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.168/304RID-0000302867unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.172/304RID-0000593415unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.176/304RID-0000538124unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.180/312RID-0000577327unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.182/312RID-0000962034unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.184/298RID-0000360138unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.192/304RID-0000631693unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.196/304RID-0000630645unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.200/304RID-0000600124unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.204/312RID-0000600124unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.206/312RID-0000445156unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.208/304RID-0000171023unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.212/304RID-0000171023unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.216/304RID-0000171023unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.61.220/304RID-0000584422unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.62.0/24256GENERAL-PRIVATE-NET-A192-8Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.63.0/24256GENERAL-PRIVATE-NET-A324-20Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.64.0/24256GENERAL-PRIVATE-NET-A160-13Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.65.0/24256GENERAL-PRIVATE-NET-A175-13Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.66.0/25128GENERAL-CORPORATE-NET-A412-38Dynamic corporate networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.66.128/2732GENERAL-PRIVATE-NET-A498-107Dynamic private networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.66.160/304RID-0000941433unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.66.164/304RID-0000938162unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.66.168/298RID-0000916465unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.66.176/304RID-0000757163unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.66.180/304RID-0000941067unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.67.0/24256GENERAL-PRIVATE-NET-A159-11Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.68.0/24256GENERAL-PRIVATE-NET-A163-10Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.0/2664RID-0000055126unknownLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.64/2732GENERAL-PRIVATE-NET-A498-91Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.96/2732GENERAL-CORPORATE-NET-A137-271Dynamic corporate networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.128/2664GENERAL-CORPORATE-NET-A163-8Dynamic corporate networkLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.192/298RID-0000911709unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.200/304RID-0000849482unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.204/304RID-0000918685unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.208/298RID-0000669364unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.216/304RID-0000624715unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.220/304RID-0000291607unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.232/304RID-0001029703unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.236/304RID-0000920149unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.240/298RID-0000480043unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.248/304RID-0000015556unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.69.252/304RID-0000848312unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.70.0/24256GENERAL-PRIVATE-NET-A463-27Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.71.32/2816GENERAL-PRIVATE-NET-A498-92Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.71.56/298RID-0000494846unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.71.64/2816RID-0000145409unknownLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.71.128/2732GENERAL-CORPORATE-NET-A137-272Dynamic corporate networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.71.176/2816GENERAL-CORPORATE-NET-A137-275Dynamic corporate networkLEGACYNov 20, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.72.0/24256GENERAL-PRIVATE-NET-A522-2Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.73.0/24256GENERAL-PRIVATE-NET-A444-9Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.74.0/23512GENERAL-PRIVATE-NET-A183-9Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.76.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.77.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.78.0/24256GENERAL-PRIVATE-NET-A412-127Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.79.0/24256GENERAL-PRIVATE-NET-A571-2Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.80.0/24256GENERAL-PRIVATE-NET-A357-40Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.81.0/24256GENERAL-PRIVATE-NET-A357-41Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.82.0/24256GENERAL-PRIVATE-NET-A357-42Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.83.0/24256GENERAL-PRIVATE-NET-A357-43Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.84.0/25128GENERAL-PRIVATE-NET-A303-14Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.84.128/2732GENERAL-CORPORATE-NET-A137-273Dynamic corporate networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.84.160/2732GENERAL-PRIVATE-NET-A498-93Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.85.0/24256GENERAL-PRIVATE-NET-A333-2Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.86.0/24256GENERAL-PRIVATE-NET-A333-3Dynamic private networkLEGACYNov 9, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.0/2664RID-0000949726unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.64/298RID-0000975613unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.72/304RID-0000971781unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.76/304RID-0000934037unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.80/304RID-0000961336unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.84/304RID-0000486602unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.88/298RID-0000328934unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.112/304RID-0000504108unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.116/304RID-0000691632unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.120/312RID-0000519663unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.122/312RID-0000128344unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.124/304RID-0000977793unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.128/304RID-0000910357unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.132/304RID-0000500394unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.136/304RID-0000972294unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.140/304RID-0000978583unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.144/298RID-0000977694unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.152/298RID-0000973730unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.160/298RID-0000973730unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.168/298RID-0000973730unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.87.176/298RID-0000973730unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous201–400 of 1,781 · page 2 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