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

80.75.13.0/24

No anonymizer space · no proxy exits in 30 days

Afranet

Announcement
this exact prefix
RPKI valid
Announced by
AS25184
Type
Hosting
Risk
50 / 100 · Medium

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.75.0.0/20
since May 2026
AS25184Hosting5Afranet

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
80.75.0.0/204,096IR-AFRANET-20010619Afranet (ORG-AA32-RIPE) · IRALLOCATED PADec 11, 2001abuse@afranet.com
└ 80.75.13.0/304Poshtiban-Taghzieh-ParsianunknownASSIGNED PAApr 16, 2024abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.4/304Pakan-Polimer-JamunknownASSIGNED PANov 8, 2025abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.8/304Salamat-Novin-IranianunknownASSIGNED PAJun 14, 2021abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.12/304Fanavaran-Tolo-ShabakeunknownASSIGNED PAJun 6, 2026abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.20/304Tose-Tejarat-MazianunknownASSIGNED PASep 5, 2018abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.28/304Farzanegan-Fars-NikounknownASSIGNED PASep 20, 2025abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.32/304bimeh-pasargadunknownASSIGNED PADec 19, 2018abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.36/304tadbir-comunknownASSIGNED PAJun 26, 2019abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.40/298CHAGALESHCHAGALESHASSIGNED PAAug 9, 2015abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.48/304Fanavaran-Toloe-ShabakehunknownASSIGNED PAAug 24, 2024abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.56/298gardeshgar-gostar-khaneye-maunknownASSIGNED PAJul 10, 2019abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.64/304Astm-Sanat-IranianunknownASSIGNED PAJan 17, 2023abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.72/298yadman-nasrunknownASSIGNED PAFeb 8, 2023abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.96/2816Kasra-ParsunknownASSIGNED PAOct 29, 2024abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.136/304MR-MOHAMMADREZA-GHOLAMIunknownASSIGNED PAMay 14, 2022abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.144/304Andishe-Pardazan-ChoganunknownASSIGNED PAJul 15, 2023abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.152/304Bimeh-KararafinunknownASSIGNED PADec 18, 2022abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.156/304mobtakeran-andisheh-nahiraunknownASSIGNED PAOct 12, 2021abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.176/298CHAGALESHChagaleshASSIGNED PANov 8, 2009abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.192/2732bime-tejarat-nounknownASSIGNED PAJan 30, 2021abuse@afranet.com
via IR-AFRANET-20010619
└ 80.75.13.224/2732kargozari-simab-goonunknownASSIGNED PAMar 16, 2021abuse@afranet.com
via IR-AFRANET-20010619

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
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 21 yr
Origin networks
1