Autonomous system
AS16351 JUNO-AS
Unclassified APNIC
Summary
Juno
hosting business isp
The netname is not a name at all. It is the registry's own internal handle for the organisation.
What it's used for
- A small network. A single IPv4 prefix announced from the United Kingdom, no IPv6, two hundred and fifty-six addresses, through one observed BGP neighbour.
Notable
- The registry holder is a private individual rather than a company, so the record names a person where most records name a business.
- The block itself is registered to a company: its technical team is the first contact, the individual is the second, and the company's abuse team is the third.
- The netname is an organisation identifier generated by the registry, made of a prefix meaning organisation, two initials, a sequence number, and the registry's own abbreviation on the end. Nobody chose it as a name.
- Those two initials belong to the individual, not to the company that operates the block, so the only human-readable part of the netname points at the wrong party.
- The AS handle is a four-letter word and the letters for an autonomous system, and that word appears nowhere else in the record.
- Three addresses were queried for reverse DNS and none returned a name.
Interesting
- When the netname field is left empty the registry fills it with the organisation handle, and that becomes the block's permanent name. It is the clearest sign that nobody had a name in mind.
- One block, one upstream, an individual holder and a company operator is the shape of a consultancy that needed its own addresses and never needed more.
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.
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS47480 | Blue Tiger Solutions Limited | 1 |
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 0 prefixes · 0 addresses IPv6 0 prefixes
This network announces no prefixes we can see.
Registry
Allocation record
- Registry
- APNIC
- Handle
AS16351- Registry name
- JUNO-AS
- Registrant
- bluetiger-mnt
- Abuse contact
- abuse@bluetigersolutions.com
- Registered
- 2006-05-22
- Last changed
- 2026-05-13
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 1 with no ROA
- ROAs
- 0 authorising AS16351
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 2 naming AS16351
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