Hostname
flooom.com
Last fetched
flooom.com resolves to 172.233.219.123, announced in 172.233.208.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. flooom.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
- 172.233.219.123
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.219.49
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.219.78
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.25
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.38
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.8
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 3.84.75.231
3.80.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 62.238.121.188
IPv6 resolution
No AAAA record for flooom.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:49
- Registrant organisation
- contact privacy inc. customer 1244991139
- Contact emails
- admin@onamae.com, flooom@naver.com, proxy@whoisprotectservice.com, sksqrqyy2x0s@contactprivacy.email
Subdomains
Showing 6 of 6 subdomains (6 per page).
Mail and authentication
Nameservers
- garrett.ns.cloudflare.com
- nadia.ns.cloudflare.com
- ns1.parklogic.com
- ns2.parklogic.com
- dns1.registrar-servers.com
- dns2.registrar-servers.com
MX records
- flooom.com
- mx156.hostedmxserver.com
Threat-feed evidence
History
Related pages
Pivot from flooom.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: "flooom.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.