AS768

AS768 is a dormant U.S. Department of Defense autonomous system registered to the Navy Network Information Center (NNIC) that currently announces zero IPv4 and zero IPv6 prefixes. ARIN's RDAP record lists the ASN's status as active, but no routing source shows it visible in the global routing table today.

The ASN was registered with ARIN on 1990-10-31 and last changed 2011-07-15, per the autnum record's top-level events. The registrant handle (NNICN-1) lists NNIC at a Virginia Beach, VA address, while the administrative/abuse contact resolves to the DoD Network Information Center, a DISA-run shared contact based in Whitehall, OH — a naming split typical of DoD-block ASN registrations rather than a discrepancy between two operators.

Routing visibility is nil: RIPEstat shows 0 of 328 IPv4 RIS peers and 0 of 322 IPv6 RIS peers seeing AS768, with zero observed BGP neighbours. CAIDA AS Rank places it at 79,459 with an empty customer cone (1 ASN, 0 prefixes, 0 addresses) and zero customer/peer/provider degree. AS768 did announce two IPv6 /48s historically — first seen 2015-07-17, last seen 2023-03-04 — but nothing is live now.

No dedicated public operator website or peering policy could be located; PeeringDB's network record for AS768 (org 18365) lists no website, no policy, and no notes. Notable usage beyond "DoD/Navy internal infrastructure" is unverified — no sourced reporting ties AS768 to a specific mission or incident. RPKI validation does not apply while no prefixes are announced.

Operator

Navy Network Information Center (NNIC), U.S. Department of Defense / U.S. Navy (registrant handle NNICN-1; admin/abuse contact resolves to DoD Network Information Center, DISA-Columbus) [Confirmed] — ARIN RDAP autnum, ARIN RDAP entity NNICN-1

Country / RIR

US, ARIN [Confirmed] — ARIN RDAP autnum

Allocated

1990-10-31 (ARIN RDAP autnum top-level "registration" event — a first-party RIR fact, not an IEEE/database artifact); last changed 2011-07-15 [Confirmed] — ARIN RDAP autnum

Org status

active per ARIN RDAP autnum status field [Confirmed] — ARIN RDAP autnum

Contacts

abuse via disa.columbus.ns.mbx.arin-registrations@mail.mil; DoD Network Information Center, 300 North James Road, Whitehall, OH 43213; registrant NNIC, 2465 Guadalcanal Road, Bldg 1265, Virginia Beach, VA 23459 [Confirmed] — ARIN RDAP entity NNICN-1 / REGIS10-ARIN

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-31 — not surfaced in Spamhaus, AbuseIPDB, abuse.ch, or NANOG archives via web search (direct per-service threat-feed API queries not performed)

Network & routing

Network type

DoD/Navy internal network infrastructure (legacy DoD-block ASN, DNIC-AS-00768 naming convention); not a commercial ISP, content network, or transit provider [Likely] — ARIN RDAP autnum

Size

dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes announced currently; customer cone = 1 ASN (itself), 0 prefixes, 0 addresses [Confirmed] — RIPEstat routing-status, CAIDA AS Rank (2026-07)

Routing/peering

NOT announced — 0 of 328 IPv4 RIS peers and 0 of 322 IPv6 RIS peers see it; CAIDA degree total 0 (customer 0, peer 0, provider 0); no upstreams or peers visible in any source [Confirmed]. Historically announced IPv6 /48s between 2015-07-17 and 2023-03-04 (first seen 2001:480:1012::/48, last seen 2001:480:1c::/48)

[Confirmed] — RIPEstat, CAIDA AS Rank

RPKI

not assessable — AS768 announces no prefixes currently, so there are no ROAs to validate against [Confirmed] — RIPEstat rpki-validation endpoint (requires --prefix; none applicable)

Notable usage

Unknown — no independently sourced reporting (news, IR filings, official DoD pages) describing specific notable usage of AS768 was located; treat as DoD/Navy internal infrastructure only [Unknown]

Related ASNs

NNIC/DoD is reported to operate multiple ASNs (AS22, AS37, AS48, AS84, AS89, AS768, AS788 among others) per third-party DB search corroboration; AS84 in particular surfaced as a distinct Navy/NNIC-operated ASN and must not be conflated with AS768

[Likely] — bgpview.io / bgp.tools search corroboration

Analyst note

Encountered as a dormant DoD/Navy ASN with no live routing announcements. ARIN RDAP is the only strong first-party source; operator/notable-usage web presence is essentially nonexistent (no dedicated website per PeeringDB and WebSearch).