Autonomous system
AS14567 SPRINGS
Hosting ARIN
Summary
Springs Hosting
hosting business infrastructure
Three netname styles, two reverse-DNS formats, and a carrier's label that names the wrong block.
What it's used for
- A hosting provider's network. 4,096 addresses across five IPv4 prefixes, with three observed BGP neighbours and no IPv6 announced.
Notable
- The company's own blocks are labelled three different ways:
SPRINGSHOSTING,SPRINGS-162-244-68, and8-30-152-0-23with no name in it at all. 206.216.17.0/24is registered toLevel 3 Parent, LLCunder the netnameLVLT-ORG-206-215.- Five of fifteen sampled addresses answered, in two formats:
host-69-244-162.springshosting.netandhost64-196-7-8.springshosting.net.
Interesting
- Both hostname formats write the address backwards, and they disagree about how much of it to include and where to put the dash. One block was set up, then another was set up years later by someone who did not look at the first.
- The carrier's netname names a range one step away from the block it is attached to. Netnames are free text and nothing validates them against the addresses they label, so a single mistyped digit survives indefinitely.
- Five blocks in four unrelated parts of the address space, ranging from a
/21down to a/24, is the portfolio of a hosting company that has bought space wherever it could find it. Nobody designs this; it accumulates. - The third netname is just the block written out with dashes, which is what the registry generates when the applicant leaves the field alone.
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 5 prefixes · 4.10K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 5 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS14567- Registry name
- SPRINGS
- Registrant
- Springs Hosting
- Abuse contact
- abuse@springshosting.com
- Registered
- 2010-12-14
- Last changed
- 2012-03-02
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Springs Hosting
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- https://www.springshosting.com
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
- 0% valid · 0 valid, 5 with no ROA
- ROAs
- 0 authorising AS14567
- ASPA
- no ASPA record
- IRR
- 80% registered · 4 of 5 announcements
- Route objects
- 4 naming AS14567
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: 446 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