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.154.16/298RID-0000093557unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.24/298RID-0000704958unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.32/304RID-0000522888unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.36/304RID-0000834142unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.40/298RID-0000840016unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.48/298RID-0000817351unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.56/304RID-0000793487unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.60/304RID-0000649045unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.64/298RID-0000016609unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.72/304RID-0000736081unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.76/304RID-0000199110unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.80/304RID-0000626072unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.84/304RID-0000896064unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.88/298RID-0000768830unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.96/298RID-0000840006unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.104/304RID-0000846778unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.108/304RID-0000359557unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.112/298RID-0000052696unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.154.120/298RID-0000084142unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.0/2732GENERAL-CORPORATE-NET-A351-11Dynamic corporate networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.32/2732RID-0000161942unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.64/298RID-0000826800unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.72/298GENERAL-CORPORATE-NET-A351-6Dynamic corporate networkLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.80/298GENERAL-CORPORATE-NET-A351-7Dynamic corporate networkLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.88/298GENERAL-CORPORATE-NET-A351-8Dynamic corporate networkLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.96/298GENERAL-CORPORATE-NET-A351-9Dynamic corporate networkLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.104/304RID-0000919383unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.108/304RID-0000840707unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.156.112/2816GENERAL-CORPORATE-NET-A316-4Dynamic corporate networkLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.0/298RID-0000221834unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.8/298RID-0000457681unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.16/304RID-0000623880unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.20/304RID-0000330906unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.24/304RID-0000776583unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.28/304RID-0000767384unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.32/304RID-0000454906unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.36/312RID-0000527822unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.38/312RID-0000019035unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.40/298RID-0000158302unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.48/298RID-0000618577unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.56/298RID-0000618577unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.64/298RID-0000158302unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.72/304RID-0000605133unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.76/304RID-0000220504unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.80/304RID-0000723543unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.84/304RID-0000330906unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.88/304RID-0000617558unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.92/304RID-0000353493unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.96/304RID-0000269441unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.100/304RID-0000330906unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.112/304RID-0000476550unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.116/304RID-0000449286unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.122/312RID-0000157061unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.124/304RID-0000318492unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.128/304RID-0000616605unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.132/312RID-0000479399unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.134/312RID-0000296309unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.136/304RID-0000528676unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.140/304RID-0000323639unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.144/304RID-0001007966unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.148/304RID-0000837077unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.152/298RID-0000330906unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.160/312RID-0000348289unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.162/312RID-0000739459unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.164/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.168/304RID-0000019909unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.172/312RID-0000488792unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.174/312RID-0000488792unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.184/298RID-0000159593unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.192/304RID-0000918214unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.196/312RID-0000598949unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.198/312RID-0000556097unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.200/304RID-0000834117unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.204/304RID-0000618284unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.208/304RID-0000304286unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.212/304RID-0000857149unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.216/298RID-0000609734unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.157.224/2732GENERAL-PRIVATE-NET-A498-183Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.158.192/304RID-0000874275unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.158.196/304RID-0000875610unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.158.200/304RID-0000804459unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.158.204/304RID-0000875940unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.158.208/2816RID-0000791396unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.158.224/304RID-0000433089unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.158.228/304RID-0000019551unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.158.232/298RID-0000867196unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.159.0/24256GENERAL-PRIVATE-NET-A966-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.40/304RID-0000487009unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.44/304RID-0000697285unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.48/304RID-0000898135unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.52/304RID-0000433395unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.56/298RID-0000117819unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.66/312RID-0000449680unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.68/304RID-0000874092unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.72/304RID-0000800470unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.78/312RID-0000194183unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.80/298RID-0000132974unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.88/304RID-0000755870unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.92/304RID-0000494823unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.96/304RID-0000625003unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.100/304RID-0000515667unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.112/304RID-0000194183unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.116/304RID-0000318502unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.120/298GENERAL-PRIVATE-NETDynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.128/2816RID-0000467744unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.144/298RID-0000467744unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.152/304RID-0000882109unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.156/304RID-0001053625unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.160/304RID-0000980135unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.164/304RID-0001054371unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.168/304RID-0001060652unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.172/304RID-0001053367unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.176/304RID-0001066724unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.180/304RID-0000697958unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.184/304RID-0001059790unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.188/304RID-0001066690unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.200/304RID-0000840526unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.204/304RID-0001064269unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.208/2816RID-0000927354unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.240/304RID-0001064530unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.244/304RID-0001066793unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.248/304RID-0001065310unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.161.252/304RID-0001061412unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.0/2664GENERAL-PRIVATE-NET-A896-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.64/298RID-0000016870unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.74/312RID-0000843540unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.76/304RID-0000260421unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.80/304RID-0000625911unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.84/304RID-0000979275unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.88/304RID-0000577327unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.92/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.96/304RID-0000895640unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.100/304RID-0001010650unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.104/304RID-0001043384unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.108/304RID-0001018639unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.112/304RID-0000453046unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.116/304RID-0001067518unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.120/304RID-0000465921unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.124/304RID-0000353524unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.162.128/25128GENERAL-PRIVATE-NET-A251-13Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.163.0/24256GENERAL-PRIVATE-NET-A357-11Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.164.0/24256GENERAL-PRIVATE-NET-A357-45Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.64/312RID-0000596481unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.66/312RID-0000614308unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.68/304RID-0000621693unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.72/304RID-0000907666unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.76/304RID-0000651226unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.80/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.84/304RID-0000766225unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.88/304RID-0000307697unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.92/304RID-0000350389unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.96/304RID-0000208102unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.100/312RID-0000060090unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.104/304RID-0000995581unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.108/304RID-0000145002unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.112/304RID-0000985811unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.116/304RID-0000693866unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.120/304RID-0000621907unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.124/304RID-0000617937unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.128/2664GENERAL-PRIVATE-NET-A951-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.192/2732GENERAL-PRIVATE-NETDynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.224/298RID-0000617937unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.232/298RID-0000898001unknownLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.240/304RID-0000627958unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.244/312RID-0000981526unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.165.248/298RID-0000627958unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.166.0/23512GENERAL-PRIVATE-NET-A951-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.0/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.4/304RID-0000262141unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.8/304RID-0000583969unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.12/304RID-0000676954unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.16/304RID-0000313562unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.20/304RID-0000481313unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.24/304RID-0000621815unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.28/304RID-0000591500unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.32/298GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.40/304RID-0001025347unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.44/304RID-0001021499unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.48/2816GENERAL-PRIVATE-NETDynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.64/2664GENERAL-PRIVATE-NET-A969-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.168.128/25128GENERAL-PRIVATE-NET-A969-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.0/304RID-0000597927unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.4/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.8/298RID-0000448446unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.16/2816RID-0000244334unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.32/2732GENERAL-CORPORATE-NET-A929-1Dynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.64/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.68/312RID-0000086803unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.72/298INFRA-AW-BIABInfrastructure networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.80/298RID-0001027217unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.88/304RID-0000482035unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.92/304RID-0001038011unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.96/2732GENERAL-PRIVATE-NET-A950-1Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.128/2664RID-0000437212unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.169.192/2664GENERAL-PRIVATE-NET-A950-2Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.0/304RID-0001000668unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.4/304RID-0000578452unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.8/304RID-0001000671unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.12/304RID-0001006632unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.170.16/304RID-0001006515unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous801–1,000 of 1,781 · page 5 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