Autonomous system
AS19779 SGFD
Unclassified ARIN
Summary
St. George Fire Department
government municipal public-safety
The AS handle SGFD is held by St. George Fire Department.
What it's used for
- The address space carries infrastructure for the St. George Fire Department, evidenced by the netname
SGFD-IPV4-NETBLOCK-01and reverse DNS entries pointing tostgeorgefire.com. - The AS announces 256 IPv4 addresses and 1 IPv6 prefix, with 4 observed neighbours, indicating a small, self-contained network typical of a municipal public safety agency rather than a transit or large-scale access provider.
Notable
- The registrant
St. George Fire Departmentmatches the AS holder and netname, confirming direct ownership of the address space. - The inventory consists of a single IPv4 /24 block and a single IPv6 /40 prefix, representing a compact and dedicated allocation for the department's operational needs.
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 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 1 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS19779- Registry name
- SGFD
- Registrant
- St. George Fire Department
- Abuse contact
- chris.richard@stgeorgefire.com
- Registered
- 2025-02-27
- Last changed
- 2025-07-07
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- SGFD
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
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 · 1 valid, 0 with no ROA
- ROAs
- 2 authorising AS19779
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 4 naming AS19779
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: 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