Hostname
cricjet.net
Last fetched
cricjet.net resolves to 2.18.64.25, announced in 2.18.64.0/24 by AKAMAI-ASN1 - Akamai International B.V. in DE. cricjet.net 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
- 2.18.64.25
2.18.64.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 2.18.64.31
2.18.64.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 2.20.13.163
- 2.20.13.176
- 23.213.186.204
23.213.200.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Elk Grove Village, US
- 23.213.186.209
23.213.200.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Elk Grove Village, US
- 23.36.162.200
23.36.176.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.36.162.223
23.36.176.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.50.131.140
23.50.140.0/22 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.50.131.154
23.50.140.0/22 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
IPv6 resolution
Attribution
akamai asn1 international
ORIGIN_AS
WHOIS identity
- Registrar
- iana:299
- Registrant organisation
- cricket wireless
- Contact emails
- domain@cricketwireless.com, stephen.harris@cricketwireless.com
Mail and authentication
Nameservers
- a1-187.akam.net
- a1-229.akam.net
- a10-66.akam.net
- a11-65.akam.net
- a16-67.akam.net
- a2-64.akam.net
- a22-64.akam.net
- a22-67.akam.net
- a3-65.akam.net
- a4-64.akam.net
- a5-66.akam.net
- 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
Threat-feed evidence
History
Related pages
Pivot from cricjet.net 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: "cricjet.net"})-[: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.