Autonomous system
AS30263 COTNET
Unclassified APNIC NSP
Summary
Cal-Ore Telephone Co.
telecom residential fiber isp
The AS handle COTNET is held by Cal-Ore Telephone Co.
What it's used for
- The address space carries residential broadband traffic, evidenced by reverse DNS entries such as
216-7-123-254-ftth-dhcp.cot.netand generic hostnames like69-36-196-0.cot.net. - The network announces 8192 IPv4 addresses across 2 prefixes and 1 IPv6 prefix, with 5 observed neighbours, indicating a regional access provider rather than a transit hub.
Notable
- Registrants for both announced IPv4 prefixes are listed as "Cal-Ore Telephone Co.; Network Operations Center" with the netname
CALORE-COTNET, aligning perfectly with the AS holder. - The address inventory consists of two /20 blocks in the 69.36.0.0/16 and 216.7.0.0/16 ranges, along with a /32 IPv6 allocation, typical for a mid-sized regional ISP.
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-14, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 8.19K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 3 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS30263- Registry name
- COTNET
- Registrant
- Cal-Ore Telephone Co.
- Abuse contact
- ipadmin@cot.net
- Registered
- 2003-08-22
- Last changed
- 2012-03-02
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Cal-Ore Telephone
- Network type
- NSP
- Scope
- North America
- Traffic ratio
- Mostly Inbound
- Peering policy
- Open
- Website
- https://www.cot.net
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 · 11 valid, 0 with no ROA
- ROAs
- 3 authorising AS30263
- ASPA
- no ASPA record
- IRR
- 100% registered · 11 of 11 announcements
- Route objects
- 11 naming AS30263
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: 442 networks and 1,771 prefixes, as published 2026-10-15. 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