Autonomous system
AS11288 IDMS101
Hosting ARIN
Summary
InfraDMS
hosting legacy
IDMS101 is InfraDMS, an infrastructure-as-a-service provider based in Columbia, Maryland. RIS sees a compact hosting network: 2 IPv4 prefixes, 3,072 addresses, no IPv6, and just 1 observed neighbour.
What it's used for
Hosted server infrastructure. InfraDMS sells bare-metal servers, private-node and cloud virtual servers, private cloud, colocation, backup, cloud storage and virtual desktop services — the space in this AS is where those workloads live. The routing agrees: 74.112.200.0/21 and 198.74.228.0/22 are both registered to InfraDMS itself (netnames IDMS-2 and IDMS-1), and the sampled reverse DNS returns 74-112-200-5.infradms.com — the templated per-address naming that hosting providers apply across a whole block. Server space wearing its operator's own rDNS, announced by its own registrant.
Notable
A single observed neighbour is the most informative number on the card. This network has one upstream and effectively no peering, which places it firmly at the leaf of the routing graph: it is a consumer of transit, not a provider of it. That rules out any transit or carrier reading despite the "infrastructure" branding, and it is a useful reminder that neighbour count, not address count, is what separates a wholesale role from a customer role.
Interesting
Both prefixes are registered to the holder and both sit in ARIN space, so there is none of the scattered multi-registrant, multi-RIR shape that marks leased or brokered address space. What you have is the ordinary silhouette of a regional managed-hosting shop: two contiguous blocks, a few thousand addresses, one upstream, and a datacentre's worth of customer servers behind it. The IPv6 absence is worth flagging as a gap for a provider that sells cloud and colocation in 2020s.
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 |
|---|---|---|
| AS17378 | TierPoint, LLC | 118 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, 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 · 3.07K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 2 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS11288- Registry name
- IDMS101
- Registrant
- InfraDMS
- Abuse contact
- support@infradms.com
- Registered
- 2009-03-04
- Last changed
- 2014-05-06
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 2 with no ROA
- ROAs
- 0 authorising AS11288
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 7 naming AS11288
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
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,773 prefixes, as published 2026-10-13. 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