IPv4 address
104.20.38.63
Last fetched
104.20.38.63 is announced in 104.20.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. and geolocates to CA. 104.20.38.63 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
- difx.com
- academy.difx.com
- admin-api.difx.com
- admin-dev-cms.difx.com
- admin-test.difx.com
- admin-test-api.difx.com
- admin-v3.difx.com
- api.difx.com
- api-dev-admin-eks.difx.com
- api-dev-eks.difx.com
- api-staging.difx.com
- api-staging-admin.difx.com
- api-v2.difx.com
- api-v3.difx.com
- api-v3-admin.difx.com
- app.difx.com
- app-admin.difx.com
- app-docs.difx.com
- apptest.difx.com
- argocd.difx.com
- argocd-dev.difx.com
- autodiscover.difx.com
- beta.difx.com
- blog.difx.com
- bot.difx.com
- bot-new.difx.com
- buybtc.difx.com
- cms-v3.difx.com
- deployment.difx.com
- dev-admin-eks.difx.com
- dev-bot.difx.com
- dev-eks-cms.difx.com
- development.difx.com
- development-auth.difx.com
- development-derivatives.difx.com
- development-features.difx.com
- development-news.difx.com
- development-orders.difx.com
- development-otc.difx.com
- development-profile.difx.com
- development-spot.difx.com
- development-wallet.difx.com
- docs.difx.com
- email.difx.com
- kibana.difx.com
- kibana-dev.difx.com
- kubedashboard.difx.com
- kubedashboard-dev.difx.com
- kubelogs.difx.com
- lyncdiscover.difx.com
Geographic detail
- City
- Toronto, CA
- Country
- CA
- Dominant city of the prefix
- Toronto, CA
Threat-feed evidence
History
Related pages
Pivot from 104.20.38.63 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.38.63"})
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.