Autonomous system
AS219178 BOGERTDEV Johannes Cornelis van den Bogert trading as Bogert.dev
Unclassified RIPE
Summary
Bogert.dev
individual ipv6 netherlands
The AS handle BOGERTDEV is held by Johannes Cornelis van den Bogert trading as Bogert.dev.
What it's used for
- The address space consists of a single IPv6 prefix,
2a06:9801:f17::/48, with no IPv4 addresses announced. - The inventory contains 1 IPv6 prefix and 0 IPv4 prefixes, observed against 2 routing neighbours.
- The operator is an individual trading as Bogert.dev, suggesting the space supports personal or small-scale professional infrastructure rather than a commercial ISP or large enterprise network.
Notable
- The registry holder and AS handle both identify Johannes Cornelis van den Bogert trading as Bogert.dev.
- The address inventory is minimal, comprising a single /48 IPv6 block with no IPv4 presence.
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-11-04, 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 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| NL | Netherlands | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS219178- Registry name
- BOGERTDEV
- Registrant
- BOGERTDEV-MNT
- Abuse contact
- info@bogert.dev
- Registered
- 2026-07-17
- Last changed
- 2026-07-17
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- BOGERTDEV
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
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 · 1 valid, 0 with no ROA
- ROAs
- 1 authorising AS219178
- ASPA
- 2 declared providers
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 1 naming AS219178
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: 453 networks and 1,853 prefixes, as published 2026-11-05. 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