Autonomous system
AS206981 Teritum Development
Unclassified RIPE
Summary
Teritum Development
business uk small
The AS handle Teritum Development is held by Teritum Development.
What it's used for
- The space carries a single IPv4 block,
87.83.112.0/24, and one IPv6 prefix,2a06:1285:dead::/48. - With 256 IPv4 addresses announced against 2 observed neighbours, the ratio indicates a small-scale access or endpoint network rather than a transit provider.
- The operator maintains a web presence at teritum.dev, suggesting the infrastructure supports specific business or development services.
Notable
- The RDAP registrant for the primary prefix is listed as "Private Customer" with an abuse contact role, which differs from the AS holder name "Teritum Development".
- The address inventory is minimal, consisting of one /24 block and a single /48 IPv6 prefix, consistent with a small private or corporate estate.
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-27, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 256 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| GB | United Kingdom | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS206981- Registry name
- TeritumDevelopment
- Registrant
- Christopher-Mountford-MNT
- Abuse contact
- abuse@teritum.dev
- Registered
- 2022-03-22
- Last changed
- 2023-01-07
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Teritum Development
- Scope
- Global
- Peering policy
- No
- IRR as-set
AS-TERITUM-DEVELOPMENT- Website
- https://teritum.dev
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 · 2 valid, 0 with no ROA
- ROAs
- 4 authorising AS206981
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 6 naming AS206981
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,852 prefixes, as published 2026-10-27. 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