Autonomous system
AS44436 TED
Unclassified RIPE Cable/DSL/ISP
Summary
Toosee Ertebatat Damavand
isp iran residential regional
The AS handle TED is held by Toosee Ertebatat Damavand.
What it's used for
- The address space carries server infrastructure, as indicated by reverse DNS entries such as
server64.tadserver.comand netnames likeTadServerandTADServer. - The network announces 1024 IPv4 addresses across 4 prefixes with only 2 observed neighbours, a ratio consistent with a regional access or hosting provider rather than a transit carrier.
- Traffic from this AS consists of web and API endpoints hosted on the operator's infrastructure, serving regional users in Iran.
Notable
- Registrants for three of the four prefixes are listed as
Tad ServerorAbuse-C Role, while the fourth prefix194.59.214.0/24is registered toNahor Hadish Design and Architecture Co., Ltdunder the netnameIR-NAHOR-20191025. - The address inventory is small and fragmented, consisting of four distinct /24 blocks from different ranges, suggesting a collection of smaller allocations rather than a single contiguous block.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-31, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 4 prefixes · 1.02K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| IR | Iran (Islamic Republic of) | 4 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS44436- Registry name
- TED
- Registrant
- Mizban Dade Pasargad
- Abuse contact
- abuse@tadserver.com
- Registered
- 2020-03-05
- Last changed
- 2025-09-16
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- MyBox
- Also known as
- Effortel
- Network type
- Cable/DSL/ISP
- Scope
- Regional
- Traffic ratio
- Balanced
- Peering policy
- Open
- Facilities
- 1 facilities
- Website
- http://www.mybox.ru
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 4 valid, 0 with no ROA
- ROAs
- 4 authorising AS44436
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 4 naming AS44436
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 447 networks and 1,845 prefixes, as published 2026-10-31. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere