Hostname
camflood.com
Last fetched
camflood.com resolves to 208.122.201.72, announced in 208.122.192.0/19 by MOJOHOST - MOJOHOST in US. camflood.com 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
- 208.122.201.72
208.122.192.0/19 · MOJOHOST - MOJOHOST · Detroit, US
IPv6 resolution
No AAAA record for camflood.com is recorded in WhisperGraph.
Attribution
mojohost
ORIGIN_AS
WHOIS identity
- Registrar
- iana:228
- Registrant organisation
- moniker privacy services
- Contact emails
- 0ebb765e3c79d37bba0b14b780a5eb1c7c4319bc21a49aca77d63c4d484b79ab@camflood.com.whoisproxy.org, 13eb430977135e7e352b2bba3b4572c3e987b90f535a5e436237d75ddad6ca3b@camflood.com.whoisproxy.org, 245d1f08f3d471e8eac98e22173a37d12c8eb6d543aedd7fd01da1ff86b3972a@camflood.com.whoisproxy.org, 490e7cb21d8f4049fd1b10ab5f1f7367895a6a117e1e97579c61a3d740645ca4@camflood.com.whoisproxy.org, 65d1fe584e9713d0b976139926d7137f442744a8d5a125a768af8f2cc9e0acbb@camflood.com.whoisproxy.org, 70075eea8cc284d24c6235eec22a2565f6b80962156538b51cdf08c2de590c00@camflood.com.whoisproxy.org, 82478434cf720e0a6c6dea95a2f62e7b91b02557c8d53855d9d086ad58fc751b@camflood.com.whoisproxy.org, 8763c0197209e6d2caefac114183d705130a5142138e0addbcaf169308bd8a96@camflood.com.whoisproxy.org, 9b3e59365613e46e7c9c65110d7e18af4594db21d511a34f8b0e385b38f0774f@camflood.com.whoisproxy.org, 9ef77b9798836d1c0c3b8e7039c563cf2d46848279bdc4d438985cb3fc02bcb7@camflood.com.whoisproxy.org, b23b786e6f953c66ad2b9763bc2126d189f1512057ad72a129784bc593d0fe67@camflood.com.whoisproxy.org
Subdomains
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
Nameservers
- ns1.mojohost.com
- ns2.mojohost.com
MX records
- mail.camflood.com
SPF policy
- a: camflood.com
- mx: camflood.com
- include: mojohost.com
- ip: 208.122.201.72
Threat-feed evidence
History
Related pages
Pivot from camflood.com 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: "camflood.com"})-[: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.