IPv4 address
104.20.44.206
Last fetched
104.20.44.206 is announced in 104.20.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. and geolocates to CA. 104.20.44.206 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
- no-data
Nutrition Label
Attribution
- Announced prefix
- 104.20.32.0/20
- Announcing network
- CLOUDFLARENET - Cloudflare, Inc.
- RIR-registered prefix
- 104.16.0.0/12
- RPKI
- valid
Anycast detection
This does not appear to be an anycast address on the three signals Canon evaluates: reverse DNS, announced-prefix width and the announcing network's peer count.
Reverse DNS
- resemble.ai
- apega.ca
- www.jobboard.apega.ca
- mibluemedical.com
- agendamiento.mibluemedical.com
- api.mibluemedical.com
- attach.mibluemedical.com
- cr.mibluemedical.com
- farmacia.mibluemedical.com
- frontapp.mibluemedical.com
- roblered.mibluemedical.com
- telemedicina.mibluemedical.com
- webapps.mibluemedical.com
- www.mibluemedical.com
- commons.mamastar.jp
- dev-image-select.mamastar.jp
- dev-static-select.mamastar.jp
- fallover-check.mamastar.jp
- image-select.mamastar.jp
- image-select-test.mamastar.jp
- manage-segment.mamastar.jp
- manage-segments-api.mamastar.jp
- staging-manage-segments-api.mamastar.jp
- static-select.mamastar.jp
- stg-commons.mamastar.jp
- stg-image-select.mamastar.jp
- stg-manage-segment.mamastar.jp
- stg-static-select.mamastar.jp
- stg-v4-archived-image.mamastar.jp
- stg-v4-image.mamastar.jp
- stg-view-lens-api.mamastar.jp
- v4-archived-image.mamastar.jp
- v4-image.mamastar.jp
- view-lens-api.mamastar.jp
- image-select.mamastar.jp.cdn.cloudflare.net
- player.radio
- assets.player.radio
- jobbox-front.mamastar.jp
Geographic detail
- City
- Toronto, CA
- Country
- CA
- Dominant city of the prefix
- Toronto, CA
Threat-feed evidence
History
Related pages
Pivot from 104.20.44.206 into the prefix, network and country that carry it.
Cypher and MCP
Reproduce this address's routing attribution against graph.whisper.security:
MATCH (ip:IPV4 {name: "104.20.44.206"})
OPTIONAL MATCH (ip)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN ap.name AS prefix, a.name AS asn, n.name AS network, c.name AS countryOr query Whisper from your own LLM workflow via the Whisper MCP server.