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.125.192/2732RID-0000222761unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.125.224/304RID-0000842679unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.125.228/304RID-0000841292unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.125.232/304RID-0000840456unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.125.248/298RID-0000900557unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.126.0/23512GENERAL-PRIVATE-NET-A163-11Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.128.0/24256GENERAL-PRIVATE-NET-A465-25Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.0/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.4/304RID-0000917898unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.8/298RID-0000452916unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.16/304RID-0000017770unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.20/304RID-0000306867unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.24/298RID-0000885206unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.32/304RID-0000809497unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.36/304RID-0000954414unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.40/298RID-0000597698unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.48/304RID-0000596228unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.129.52/304RID-0000719687unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.0/298RID-0001046860unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.8/298RID-0000467744unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.16/2816RID-0000467744unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.32/304RID-0000988518unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.36/304RID-0001048499unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.40/304RID-0000172306unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.44/304RID-0001046491unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.48/298RID-0001045005unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.56/298RID-0000518184unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.64/2732GENERAL-PRIVATE-NET-A498-467Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.96/2732GENERAL-PRIVATE-NET-A498-468Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.128/2732GENERAL-PRIVATE-NET-A498-469Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.160/2732GENERAL-PRIVATE-NET-A498-470Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.192/304RID-0001033592unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.196/304RID-0001041911unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.200/304RID-0000848519unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.204/304RID-0000843807unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.208/298RID-0000626603unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.216/304RID-0000993164unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.131.220/304RID-0001049338unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.16/304RID-0000670109unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.20/304RID-0000495139unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.24/304RID-0000523097unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.28/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.64/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.68/304RID-0000888062unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.72/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.76/304RID-0000453885unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.88/304RID-0000302375unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.92/304RID-0000546437unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.112/298RID-0000714434unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.120/304RID-0001065075unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.124/304RID-0000957863unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.160/304RID-0000739459unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.164/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.168/298RID-0000584477unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.240/304RID-0000207565unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.244/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.132.248/298RID-0000584422unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.0/304RID-0000228192unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.4/304RID-0000301007unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.16/298RID-0000488792unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.24/304RID-0000977466unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.28/304RID-0000927179unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.32/304RID-0000985026unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.36/304RID-0000980034unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.40/304RID-0000979635unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.44/304RID-0000978631unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.48/304RID-0000962783unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.52/304RID-0000533296unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.56/304RID-0000962783unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.60/304RID-0000631699unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.64/2816RID-0000682713unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.80/304RID-0000740456unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.84/304RID-0000972635unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.88/304RID-0000976858unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.92/304RID-0000508406unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.96/298RID-0000349774unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.104/298RID-0000970391unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.112/304RID-0000320705unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.116/304RID-0000863694unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.120/298RID-0000751511unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.128/298RID-0000610220unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.136/298RID-0000721666unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.144/298RID-0000768200unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.152/298RID-0000158747unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.160/298RID-0000621708unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.168/298RID-0000930335unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.176/2816RID-0000973460unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.192/2816RID-0000978822unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.208/304RID-0000459733unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.212/304RID-0000780627unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.216/304RID-0000689827unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.220/304RID-0000689827unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.224/304RID-0000979838unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.228/304RID-0000981283unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.232/304RID-0000980967unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.236/304RID-0000638428unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.240/304RID-0000855507unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.244/304RID-0000645718unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.248/304RID-0000918609unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.133.252/304RID-0000995722unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.0/304RID-0000884676unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.4/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.8/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.12/304RID-0000886963unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.16/304RID-0000964926unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.20/304RID-0000597119unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.24/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.28/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.32/2732RID-0000273314unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.134.128/2732GENERAL-PRIVATE-NETDynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.135.32/304RID-0000772896unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.135.36/304RID-0000602312unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.135.48/304RID-0001014021unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.135.52/304RID-0000595862unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.135.56/304RID-0000970979unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.135.60/304RID-0000876424unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.136.0/221,024GENERAL-PRIVATE-NETDynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.140.0/221,024GENERAL-PRIVATE-NET-A333-4Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.144.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.0/2816GENERAL-PRIVATE-NET-A498-175Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.16/2816GENERAL-PRIVATE-NET-A498-176Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.32/2732GENERAL-PRIVATE-NET-A857-2Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.64/2816GENERAL-PRIVATE-NET-A498-177Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.88/304RID-0000614929unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.92/304RID-0000203661unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.96/304RID-0001006323unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.100/304RID-0000602343unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.104/298RID-0000212201unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.128/304RID-0000612447unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.132/304RID-0000608156unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.136/298GENERAL-PRIVATE-NET-A530-13Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.144/304RID-0000644063unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.148/304RID-0001019035unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.152/298RID-0000325620unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.160/304RID-0000796092unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.164/304RID-0000523521unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.168/304RID-0000523521unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.172/304RID-0000511396unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.176/298RID-0000599417unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.184/304RID-0000262141unknownLEGACYAug 14, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.188/304RID-0000262141unknownLEGACYAug 14, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.192/304RID-0000055611unknownLEGACYAug 14, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.196/304RID-0000631699unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.200/304RID-0000323924unknownLEGACYAug 14, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.204/304RID-0000214579unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.208/304RID-0000362899unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.212/304RID-0000265202unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.216/304RID-0000610923unknownLEGACYAug 14, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.220/304RID-0000559919unknownLEGACYAug 14, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.224/304RID-0000980468unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.228/304RID-0000623537unknownLEGACYAug 14, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.232/304RID-0000583969unknownLEGACYAug 14, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.236/304RID-0000430727unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.240/304RID-0000358739unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.244/304RID-0000348289unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.248/304RID-0000430042unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.145.252/304RID-0001065997unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.146.0/23512GENERAL-PRIVATE-NET-A444-15Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.148.0/24256GENERAL-CORPORATE-NETDynamic corporate networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.149.0/24256GENERAL-PRIVATE-NET-A438-8Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.150.128/25128RID-0000005375unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.151.0/24256RID-0000005375unknownLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.0/304RID-0000844535unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.4/304RID-0000121317unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.8/304RID-0000319347unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.12/304RID-0000448678unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.16/2816RID-0000019035unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.32/304RID-0000752595unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.36/304RID-0000841806unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.40/304RID-0000736070unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.44/304RID-0000736070unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.48/304RID-0000259140unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.52/304RID-0000227796unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.56/304RID-0000756943unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.60/304RID-0000678686unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.64/2732GENERAL-PRIVATE-NET-A498-259Dynamic private networkLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.96/304RID-0000194837unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.100/304RID-0000270353unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.104/304RID-0000769925unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.108/304RID-0000846106unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.112/304RID-0000478460unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.116/304RID-0000454615unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.120/304RID-0001017448unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.124/304RID-0000843229unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.128/304RID-0000065601unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.132/304RID-0000845809unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.136/304RID-0000803843unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.140/304RID-0000901753unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.144/304RID-0000845391unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.148/304RID-0001044530unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.152/304RID-0000845809unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.156/304RID-0000800062unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.160/304RID-0000559152unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.164/304RID-0000845740unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.168/304RID-0000845854unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.172/304RID-0000705022unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.176/298RID-0000846024unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.184/298GENERAL-CORPORATE-NET-A351-5Dynamic corporate networkLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.224/304RID-0000910381unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.152.228/304RID-0000705022unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous601–800 of 1,781 · page 4 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