LAYER3 INTEL
Get started
Sign in
Data as of Nov 9, 2026

141.39.0.0/16

6 residential-proxy exits · 30 days

Verein zur Foerderung eines Deutschen Forschungsnetzes e.V.

Announcement
this exact prefix
RPKI valid
Announced by
AS680
Type
Business

Residential-proxy exits

Proxy exits
6
<0.01% of its addresses · 30 days
Spread
5 of 256
/24s with at least one exit
Providers
15
selling exits here
Oct 10, 2026 – Nov 8, 2026

Exits seen per day

189 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
141.39.214.0/2402
141.39.185.0/2401
141.39.193.0/2401
141.39.208.0/2401
141.39.224.0/2401

Proxy providers listing exits

  • AnyIP
  • BottingTools
  • CatProxies
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • Geonode
  • InfiniteProxies
  • LemonBright
  • NovaProxy
  • ProxyEmpire
  • ProxyGeo
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
141.39.220.0/22
since Feb 2024
AS211286BusinessVerein zur Foerderung eines Deutschen Forschungsnetzes e.V.
141.39.220.0/24
since Apr 2023
AS211286BusinessVerein zur Foerderung eines Deutschen Forschungsnetzes e.V.
141.39.221.0/24
since Apr 2023
AS211286BusinessVerein zur Foerderung eines Deutschen Forschungsnetzes e.V.
141.39.222.0/23
since Apr 2023
AS211286BusinessVerein zur Foerderung eines Deutschen Forschungsnetzes e.V.
141.39.222.0/24
since Apr 2023
AS211286BusinessVerein zur Foerderung eines Deutschen Forschungsnetzes e.V.
141.39.223.0/24
since Apr 2026
AS211286BusinessVerein zur Foerderung eines Deutschen Forschungsnetzes e.V.

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
141.39.0.0/1665,536DE-DFN-960220Verein zur Foerderung eines Deutschen Forschungsnetzes e.V. (ORG-DV1-RIPE) · DELEGACY—abuse@dfn.de
└ 141.39.0.0/1732,768DT-IT-BDeutsche Telekom IT GmbHLEGACY—abuse@dfn.de
via DE-DFN-960220
└ 141.39.128.0/1816,384KRI-MUCPKlinikum rechts der IsarLEGACY—abuse@dfn.de
via DE-DFN-960220
└ 141.39.192.0/204,096FH-ANSBACHHochschule AnsbachLEGACY—abuse@dfn.de
via DE-DFN-960220
└ 141.39.208.0 - 141.39.218.2552,816GRZLG-NETLeuphana Universitaet LueneburgLEGACYFeb 18, 2003abuse@dfn.de
via DE-DFN-960220
└ 141.39.219.0/24256DFN-MSPDFN VereinLEGACYNov 30, 2011abuse@dfn.de
via DE-DFN-960220
└ 141.39.220.0/221,024MPISWS-KLMax-Planck-Institut fuer Informatik (ORG-MFI3-RIPE) · DELEGACYSep 20, 2006abuse@measurement.network
└ 141.39.220.0/23512MSMT-NTWRK-01-02unknownLEGACYApr 4, 2023abuse@measurement.network
via MPISWS-KL
└ 141.39.220.0/24256MSMT-NTWRK-01unknownLEGACYMar 31, 2023abuse@measurement.network
via MSMT-NTWRK-01-02
└ 141.39.220.0/298MSMT-NTWRK-LPBCK-01unknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-01
└ 141.39.220.16/2816MSMT-NTWRK-01-ARCHWAR-01unknownLEGACYFeb 6, 2025abuse@measurement.network
via MSMT-NTWRK-01
└ 141.39.220.32/2816MSMT-NTWRK-TRNSF-01unknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-01
└ 141.39.220.32/312MSMT-NTWRK-TRNSF-01-AS59645unknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-01
└ 141.39.220.34/312MSMT-NTWRK-TRNSF-01-TOBERunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-01
└ 141.39.220.36/312MSMT-NTWRK-TRNSF-01-GW01GW02DUSunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-01
└ 141.39.220.38/312MSMT-NTWRK-TRNSF-01-AS50629unknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-01
└ 141.39.220.40/312MSMT-NTWRK-TRNSF-01-AS58299unknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-01
└ 141.39.220.44/312MSMT-NTWRK-TRNSF-01-TOSBRunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-01
└ 141.39.220.46/312MSMT-NTWRK-TRNSF-01-SBRLOCunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-01
└ 141.39.220.48/298MSMT-NTWRK-01-DNS-SCANunknownLEGACYMar 5, 2024abuse@measurement.network
via MSMT-NTWRK-01
└ 141.39.220.56/304MSMT-NTWRK-01-MNTRNG-HSTunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-01
└ 141.39.220.64/2732MSMT-NTWRK-01-SERVICES-DUSunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-01
└ 141.39.220.96/2816MSMT-NTWRK-01-SERVICES-AMSunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-01
└ 141.39.220.96/304MSMT-NTWRK-LPBCK-01-AMSunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-01-SERVICES-AMS
└ 141.39.220.100/304MSMT-NTWRK-TRNSF-01-AMSunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-01-SERVICES-AMS
└ 141.39.220.128/25128MSMT-NTWRK-01-AFunknownLEGACYOct 2, 2023abuse@measurement.network
via MSMT-NTWRK-01
└ 141.39.220.128/2664MSMT-NTWRK-01-AF-COMPunknownLEGACYOct 2, 2023abuse@measurement.network
via MSMT-NTWRK-01-AF
└ 141.39.220.192/2664MSMT-NTWRK-01-AF-SCANunknownLEGACYOct 2, 2023abuse@measurement.network
via MSMT-NTWRK-01-AF
└ 141.39.221.0/24256MSMT-NTWRK-02unknownLEGACYMar 31, 2023abuse@measurement.network
via MSMT-NTWRK-01-02
└ 141.39.221.0/298MSMT-NTWRK-LPBCK-02unknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-02
└ 141.39.221.16/2816MSMT-NTWRK-02-ARCHWAR-02unknownLEGACYFeb 6, 2025abuse@measurement.network
via MSMT-NTWRK-02
└ 141.39.221.32/2816MSMT-NTWRK-TRNSF-02unknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-02
└ 141.39.221.32/312MSMT-NTWRK-TRNSF-02-AS59645unknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-02
└ 141.39.221.34/312MSMT-NTWRK-TRNSF-02-AS210122-01unknownLEGACYMay 19, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-02
└ 141.39.221.36/304MSMT-NTWRK-02-MNTRNG-HSTunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-02
└ 141.39.221.40/312MSMT-NTWRK-TRNSF-02-AS210122-02unknownLEGACYMay 19, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-02
└ 141.39.221.44/312MSMT-NTWRK-TRNSF-02-TOSBRunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-02
└ 141.39.221.46/312MSMT-NTWRK-TRNSF-02-SBRLOCunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-TRNSF-02
└ 141.39.221.56/321MSMT-NTWRK-02-V6-HNPTunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-02
└ 141.39.221.64/2816MSMT-NTWRK-02-SERVICES-BERunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-02
└ 141.39.221.128/25128MSMT-NTWRK-02-NETWORKS-SBRunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-02
└ 141.39.221.128/2816MSMT-NTWRK-02-SERVICES-SBRunknownLEGACYMar 5, 2025abuse@measurement.network
via MSMT-NTWRK-02-NETWORKS-SBR
└ 141.39.221.144/2816MSMT-NTWRK-02-HNET-DEVunknownLEGACYJun 27, 2024abuse@measurement.network
via MSMT-NTWRK-02-NETWORKS-SBR
└ 141.39.221.160/2732MSMT-NTWRK-02-AF-SCANunknownLEGACYMar 5, 2024abuse@measurement.network
via MSMT-NTWRK-02-NETWORKS-SBR
└ 141.39.221.192/2664MSMT-NTWRK-02-AF-COMPunknownLEGACYMar 5, 2024abuse@measurement.network
via MSMT-NTWRK-02-NETWORKS-SBR
└ 141.39.222.0/23512MSMT-NTWRK-03-04unknownLEGACYApr 4, 2023abuse@measurement.network
via MPISWS-KL
└ 141.39.222.0/24256MSMT-NTWRK-03unknownLEGACYMar 31, 2023abuse@measurement.network
via MSMT-NTWRK-03-04
└ 141.39.222.128/25128MSMT-NTWRK-03-DNSMTUunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-03
└ 141.39.222.128/2664MSMT-NTWRK-03-DNSMTU-TRNSFRunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-03-DNSMTU
└ 141.39.222.192/2816MSMT-NTWRK-03-DNSMTU-NOFRAGDROP-PMTUDunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-03-DNSMTU
└ 141.39.222.208/2816MSMT-NTWRK-03-DNSMTU-FRAGD-PMTUDunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-03-DNSMTU
└ 141.39.222.224/2816MSMT-NTWRK-03-DNSMTU-NOFRAGDROP-NOPMTUDunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-03-DNSMTU
└ 141.39.222.240/2816MSMT-NTWRK-03-DNSMTU-FRAGDROP-NOPMTUDunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-03-DNSMTU
└ 141.39.223.0/24256MSMT-NTWRK-04unknownLEGACYMar 31, 2023abuse@measurement.network
via MSMT-NTWRK-03-04
└ 141.39.223.96/2732MSMT-NTWRK-04-ESECunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-04
└ 141.39.223.128/25128MSMT-NTWRK-04-DNSMTUunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-04
└ 141.39.223.128/2664MSMT-NTWRK-04-DNSMTU-TRNSFRunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-04-DNSMTU
└ 141.39.223.192/2816MSMT-NTWRK-04-DNSMTU-NOFRAGDROP-PMTUDunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-04-DNSMTU
└ 141.39.223.208/2816MSMT-NTWRK-04-DNSMTU-FRAGD-PMTUDunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-04-DNSMTU
└ 141.39.223.224/2816MSMT-NTWRK-04-DNSMTU-NOFRAGDROP-NOPMTUDunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-04-DNSMTU
└ 141.39.223.240/2816MSMT-NTWRK-04-DNSMTU-FRAGDROP-NOPMTUDunknownLEGACYApr 23, 2026abuse@measurement.network
via MSMT-NTWRK-04-DNSMTU
└ 141.39.224.0/204,096UNILE-LAN2Universitaet LeipzigLEGACYFeb 15, 2010abuse@dfn.de
via DE-DFN-960220
└ 141.39.240.0/204,096FH-MUENCHEN-NETHochschule MuenchenLEGACY—abuse@dfn.de
via DE-DFN-960220

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

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Origin network

AS680

DE
Name
Verein zur Foerderung eines Deutschen Forschungsnetzes e.V.
Type
Education
Registered
Sep 1, 1993
Domain
dfn.de
Website
www.dfn.de
Industry
Internet Service Provider (ISP)
Spamhaus ASN-DROP
not listed
Tor exits
2