Hostname
digalert.org
Last fetched
digalert.org resolves to 198.169.62.30, announced in 198.169.62.0/24 by DIGALERT - Underground Service Alert of Southern California in US. digalert.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for digalert.org is recorded in WhisperGraph.
Attribution
underground alert of southern california
ORIGIN_AS
WHOIS identity
- Registrar
- iana:3827
- Registrant organisation
- dig alert
- Contact emails
- ha76959u2u7@networksolutionsprivateregistration.com, digalert.org@domainsbyproxy.com, uv7ey8rg75n@networksolutionsprivateregistration.com, xk5gf5tn4e7@networksolutionsprivateregistration.com, yz5j65um2ha@networksolutionsprivateregistration.com, z63hx8338g3@networksolutionsprivateregistration.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns1.digalert.org
- ns2.digalert.org
MX records
- mail.digalert.org
SPF policy
- ip: 198.169.62.0/23
- ip: 198.169.63.0/23
- include: _spf.psm.knowbe4.com
- include: _spf.ndpcci.com
- include: stspg-customer.com
- a: digalert.org
- mx: digalert.org
- a: mail.digalert.org
- a: newtin.digalert.org
- a: newtina.digalert.org
- a: newtinb.digalert.org
- a: newtinlts.digalert.org
Threat-feed evidence
History
Related pages
Pivot from digalert.org into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "digalert.org"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.