AS313
Operated by DNIC-ASBLK-00306-00371 - United States Department of Defense (DoD).
Summary
- // analyst note
- Dormant/legacy DoD ASN. WHOIS resolves to the U.S. DoD via DNIC/DISA; AS carries no active routing and last appeared in the global table in early 2023 (RIPEstat 2023-02-07, bgp.he.net early 2023). One historical peer AS6045 (DoD/DISA). CAIDA AS Rank unavailable (HTTP 502).
- // security note
- NEUTRAL/DATED: no notable public abuse signal found as of 2026-06-28; absent from Spamhaus ASN-DROP, ipapi.is top-1000 abusive ASNs, AbuseIPDB, FraudGuard, and NANOG archives.
About this ASN.
AS313 is a legacy autonomous system number registered under ARIN to the United States Department of Defense (DoD), administered through the DoD Network Information Center (DNIC) and operated by the Defense Information Systems Agency (DISA) from Columbus, Ohio. It sits inside the DoD ASN block DNIC-ASBLK-00306-00371, which spans AS306 through AS371. The key triage point for AS313 is that it is dormant on the public Internet: RIPEstat reports the AS as not announced, with zero IPv4 and zero IPv6 prefixes, zero RIS peers seeing it (0/323 v4, 0/321 v6), and zero observed neighbours as of 2026-06-27. RIPE RIS last observed AS313 originating a route on 2023-02-07 (prefix 214.38.160.0/24), and Hurricane Electric likewise places its last global-table visibility in early 2023. Historically the AS originated DoD-reserved 214.x.x.x address space — bogon space that does not route on the civilian Internet — with one historical BGP peer, AS6045 (also DoD/DISA). The allocated date 1989-06-30 is read from the RDAP autnum object's top-level registration event, the authoritative ARIN registry fact; entity-level dates (org USDDD 2007-01-12, contact MIL-HSTMST-ARIN 1993-05-26, REGIS10-ARIN 2009-06-24) are contact/record dates and were correctly excluded as decoys. No notable public abuse signal was found as of 2026-06-28 — AS313 is absent from Spamhaus ASN-DROP, the ipapi.is top-1000 abusive-ASN list, AbuseIPDB, and NANOG archives. A separately documented "313 Team" Iran-aligned DDoS actor exists but has no operational connection to AS313; the naming overlap is coincidental. CAIDA AS Rank was unavailable at query time (HTTP 502), so rank and customer cone could not be assessed.
- Operator
- United States Department of Defense (DoD), via the DoD Network Information Center (DNIC), administered by DISA (ARIN registrant handle USDDD, Columbus, OH) [Confirmed] — ARIN RDAP autnum/313, bgp.tools/as/313
- Country / RIR
- US, ARIN [Confirmed] — RIPEstat abuse-contact-finder (authoritative_rir: arin)
- Allocated
- 1989-06-30 (ARIN registry date from RDAP autnum top-level registration event — NOT an IEEE date; IEEE publishes no ASN dates); last changed 2025-09-12 [Confirmed] — ARIN RDAP autnum top-level events
- Org status
- active U.S. federal agency (DISA, a DoD combat support agency); ARIN registration active (last changed 2025-09-12) but the AS is not actively routing [Confirmed] — ARIN RDAP, bgp.tools/as/313
- Contacts
- abuse/NOC disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil (Network DoD, MIL-HSTMST-ARIN), +1-844-347-2457 ext2, DISA-Columbus, 300 North James Road, Whitehall, OH 43213; admin/tech disa.columbus.ns.mbx.arin-registrations@mail.mil (REGIS10-ARIN); registrant org 3990 E. Broad Street, Columbus, OH 43218[Confirmed] — ARIN RDAP entities
Security/abuse context (NEUTRAL, DATED)
no notable public abuse signal found as of 2026-06-28 — absent from Spamhaus ASN-DROP (425 entries checked), ipapi.is top-1000 abusive ASNs, AbuseIPDB (404), FraudGuard (404), and NANOG archives. The unrelated "313 Team" Iran-aligned DDoS actor is a coincidental naming overlap, not connected to this ASN
Network & routing
- Network type
- U.S. federal government / military network; legacy DoD ASN within block DNIC-ASBLK-00306-00371 (AS306–AS371); AS313 itself is dormant/unrouted [Confirmed] — ARIN RDAP, bgp.tools/as/313
- Size
- dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; not announced; 0 observed neighbours [Confirmed] — RIPEstat routing-status / as-overview / announced-prefixes (2026-06-27)
- Routing/peering
- NOT announced — 0 RIS peers seeing it (0/323 v4, 0/321 v6); first seen 2013-11-06 (214.27.145.0/24), last seen 2023-02-07 (214.38.160.0/24); one historical BGP peer AS6045 (DoD/DISA); no commercial upstreams. No PeeringDB entry exists [Confirmed for routing; Unknown for any active peering policy] — RIPEstat routing-status, bgp.he.net/AS313
- RPKI
- not assessable — AS313 announces no prefixes, so there are no ROAs to validate; RIPEstat rpki-validation skipped (no prefix to supply) [Unknown] — RIPEstat rpki-validation
- Notable usage
- legacy allocation in the DoD NIC block; historically originated DoD-reserved 214.x.x.x space (bogon, not globally routable); the DoD NIC (DISA) manages DoD IP address space and operates the G root name server. AS313 itself appears unused today [Likely] — bgp.he.net/AS313, ipinfo.io/AS313
- Related ASNs
- AS6045 (DoD/DISA, AS313's one historical peer); AS306–AS371 share the DNIC block DNIC-ASBLK-00306-00371 [Confirmed] — bgp.he.net/AS313, ARIN RDAP
- Analyst note
- Encountered as a dormant legacy DoD ASN; WHOIS resolves to the U.S. DoD via DNIC/DISA, but the AS carries no active routing and last appeared in the global table in early 2023. Clean, inactive ASN. CAIDA AS Rank unavailable (HTTP 502).